Hello guys! first of all sorry for my English!...well i messed up my u8800-51 and i cant get it to work, i´ve read most of related posts, but nothing work, so i'll try to explay what happened, i hope u understand my issue and help me...
Ok i had a 2.3.5 GB non-official installed, from androidmovida.. my phone was working just fine, but due to all the apps and media it was kind of slowing down, so i restored it to factory settings... when i did this, my phone started up normal, and it was almost perfect again, but i realized that even without any app installed i had 800mb of the ROM occupied, leaving me less than 200mb, this was just wrong, the ammount of memory used just after a factory reset should be around 350mb... so i installed cwm 5.0.2.7 and booted it to recovery mode, here i pressed;
wipe data/factory reset
wipe dalvik cache
and what i think that screwed my phone..i went to mount and storage and pressed format /system...
Since then my phone didnt start, but i was able to get into the recovery mode... so i downoaded the stock 2.2 froyo from huawei
(this page is in spanish cuz the phone is sold in Venezuela).
i formated my SD card, and put the dload folder in its root and the update process started, but failed...
now i cant even get to the recovery mode, ive tride the process to install the fw a million times and it keeps failling..
and i just can get to the updating process or to the pink screen..if i connect my phone and leave it connected it shows up the logo and turn off, and repeat over and over..
my guess is that somehow i cant install the rom because the memory is almost full, but i have no idea of how to clear it!
if any of u guys can help me i would appriciate it a lot!!!
again sorry for my English and for the long post, but i wanted to be specific so you dont waste time telling me to do things ive already done! thank you!!!!
maxsdaspot said:
Hello guys! first of all sorry for my English!...well i messed up my u8800-51 and i cant get it to work, i´ve read most of related posts, but nothing work, so i'll try to explay what happened, i hope u understand my issue and help me...
Ok i had a 2.3.5 GB non-official installed, from androidmovida.. my phone was working just fine, but due to all the apps and media it was kind of slowing down, so i restored it to factory settings... when i did this, my phone started up normal, and it was almost perfect again, but i realized that even without any app installed i had 800mb of the ROM occupied, leaving me less than 200mb, this was just wrong, the ammount of memory used just after a factory reset should be around 350mb... so i installed cwm 5.0.2.7 and booted it to recovery mode, here i pressed;
wipe data/factory reset
wipe dalvik cache
and what i think that screwed my phone..i went to mount and storage and pressed format /system...
Since then my phone didnt start, but i was able to get into the recovery mode... so i downoaded the stock 2.2 froyo from huawei
(this page is in spanish cuz the phone is sold in Venezuela).
i formated my SD card, and put the dload folder in its root and the update process started, but failed...
now i cant even get to the recovery mode, ive tride the process to install the fw a million times and it keeps failling..
and i just can get to the updating process or to the pink screen..if i connect my phone and leave it connected it shows up the logo and turn off, and repeat over and over..
my guess is that somehow i cant install the rom because the memory is almost full, but i have no idea of how to clear it!
if any of u guys can help me i would appriciate it a lot!!!
again sorry for my English and for the long post, but i wanted to be specific so you dont waste time telling me to do things ive already done! thank you!!!!
Click to expand...
Click to collapse
You need a micro sd reader and hook it up to a computer than copy the stock gb over and delete the old froyo. You should've asked.
I've read this may work, but android movida was closed down.
Try this.
Sent from my u8800-51 on stallion.
Somcom3X said:
You need a micro sd reader and hook it up to a computer than copy the stock gb over and delete the old froyo. You should've asked.
I've read this may work, but android movida was closed down.
Try this.
Sent from my u8800-51 on stallion.
Click to expand...
Click to collapse
sorry its embarrasing i have to ask, but i'm new with android so im a little lost! but according to what i got to learn last night trying to make my phone come back to life, there's no GB stock for the u8800-51, actually the only stock fw in huawei was the one i downloaded, and the one i installed from androidmovida required froyo to be succesfully updated..anyways ill download GB to see what happens, but if you could be a little more specific it would be nice, buecause as i said, i just learned a few things last night!!
Thank you very much for your help!
http://forum.xda-developers.com/showthread.php?t=1698308
Sent from my u8800-51 on stallion.
Somcom3X said:
http://forum.xda-developers.com/showthread.php?t=1698308
Sent from my u8800-51 on stallion.
Click to expand...
Click to collapse
once again update failed, i intended wuith 3 different sd cards but nothing...
http://forum.xda-developers.com/showthread.php?t=1889305
what if i do what it says in Reverting to Stock Froyo? id rather ask first...thou i cant mess my phone any more xD
trank you again!!
maxsdaspot said:
once again update failed, i intended wuith 3 different sd cards but nothing...
http://forum.xda-developers.com/showthread.php?t=1889305
what if i do what it says in Reverting to Stock Froyo? id rather ask first...thou i cant mess my phone any more xD
trank you again!!
Click to expand...
Click to collapse
Can you access pink screen?
Sent from my u8800-51 on stallion.
Somcom3X said:
Can you access pink screen?
Sent from my u8800-51 on stallion.
Click to expand...
Click to collapse
yes i can acces pink screen!
http://forum.xda-developers.com/showthread.php?p=27121257
Ask zcux in priv message.
Sent from my u8800-51 on stallion.
Somcom3X said:
http://forum.xda-developers.com/showthread.php?p=27121257
Ask zcux in priv message.
Sent from my u8800-51 on stallion.
Click to expand...
Click to collapse
jeje i spent the whole day yesterday trying to fix it, and now its working perfectly, i had a lot of problems, so i made an image of every state and a lil tutorial for myself of every step just in case...i dont know if it would be usefull if i publish all of it in here, since i just did what was said in many threads jeje, so what you think?
and bu the way thanks for all the help!!
maxsdaspot said:
jeje i spent the whole day yesterday trying to fix it, and now its working perfectly, i had a lot of problems, so i made an image of every state and a lil tutorial for myself of every step just in case...i dont know if it would be usefull if i publish all of it in here, since i just did what was said in many threads jeje, so what you think?
and bu the way thanks for all the help!!
Click to expand...
Click to collapse
Publish it. It wont hurt anyone.
Sent from my u8800-51 on stallion.
Related
This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!
Folks,
I was playing around with the roms and BAM
My phone wont start anymore, it keeps hanging on the Android logo from Kyrillos 7.
I tried flashing other roms, but there's no help here...
Help...
Please
May the phone gods be with me........ 8-0
I'm still able to get in the download, so I guess he's not totaly bricked, right????
factory reset from recovery and reboot it might take a while.
RafayelG said:
factory reset from recovery and reboot it might take a while.
Click to expand...
Click to collapse
problem is that it keeps hanging in the ANDROID logo that shines, then suddenly stops, and resets this logo and it all starts all over, very strange...
I'm also able to install the Destiny Rom, and it boots well, but after xxx minutes this version also locks....
I had no problems with K7 OC before (only it locked after restart some days later, that was the prob)
How can I completely reset my phones internal memory?
Could this be unrepairably damaged?
SOLVED !
I can sleep good now !!!!
sorry, I panicked, because I tried several times and nothing worked.
Thanks for the advice !
(can I delete this topic?)
could you explain your solution?
mankokoma said:
could you explain your solution?
Click to expand...
Click to collapse
Of course
I formatted with Pc software at first.
I got many times locked at startup (mostly after installing programs, so the phone needs access to the SD)
I installed K7, then flashed the G3rom into it.
And then, most important:
I formatted the SD card from within the Clockwork Manager CWM.
Of course, this erased both partitions (so make backup), but at least now it works
Do you have similar problems?
no, not yet... but maybe it'll help in future & others & just curious... where's the tnx button in this app?
Sent from my GT-I5800 using XDA
Hello, while I was testing 2.3.5 witch was great except that the mobile network was not woorking at all. So I decided that I needed too downgrade. And when I was browsing the phone I accidentally found this way.
This has not been proofed by anyone else I think.
Disclaimer: I do not take the resposibility for your device.
1. Put the dload on the root of SD-card (I used 138sp4)
2. Then go to storage in preferences. Head too the bottom then choose "upgrade SD-card". The phone blacked out, started up and installed 2.2
3. The phone boots up in recovery because of many errors. I choose wipe data/chache and wipe chache and reboot.
4. The phone rebooted and I am back to 2.2.2 from 2.3.5.
This method keeps the start-boot-picture (does not know if the other sulutions keeps it).
Sorry for my bad grammar on some of the words. I just wrote them down and did not have the time to fix them.
Hmmm...interesting....maybe I should try 2.3.5 even if I have the Atmel screen. :/
Sent from my IDEOS X5 using XDA App
UnknownAX said:
Hmmm...interesting....maybe I should try 2.3.5 even if I have the Atmel screen. :/
Sent from my IDEOS X5 using XDA App
Click to expand...
Click to collapse
I have atmel screen but I like it because i wear gloves and the screen is so sensitive that it responds thrugh them.
I was forced to downgrade from 3.2.5 to 2.2.2 for the exacly same reason and i tryied that same way you did and i couldnt do it, i got a message saying something like "there are no upgrade firmware inside the SD card". So i used the root & replace boot and recovery files to downgrade what was a sucess. Got the same issues as you with the boot but the "wipe data/chache" from recovery resolved it.
jopamasi said:
I was forced to downgrade from 3.2.5 to 2.2.2 for the exacly same reason and i tryied that same way you did and i couldnt do it, i got a message saying something like "there are no upgrade firmware inside the SD card". So i used the root & replace boot and recovery files to downgrade what was a sucess. Got the same issues as you with the boot but the "wipe data/chache" from recovery resolved it.
Click to expand...
Click to collapse
Ok, maybe it does not work for everyone but what 2.2 version did you use. For exampe I used the 138sp4(international (the last(I think) 2.2.2 from Huawei))
areedw said:
Ok, maybe it does not work for everyone but what 2.2 version did you use. For exampe I used the 138sp4(international (the last(I think) 2.2.2 from Huawei))
Click to expand...
Click to collapse
The version i used was/is U8800V100R001C00B138SP04, so as far i can see it's the same as yours correct me if i'm wrong. But as far i could read about good/bad reports for 3.2.5 and all the different problems different people having version and same phones making me belive what's possible for one's arent for others.
areedw said:
I have atmel screen but I like it because i wear gloves and the screen is so sensitive that it responds thrugh them.
Click to expand...
Click to collapse
THROUGH gloves? Omg xD
Sent from my IDEOS X5 using XDA App
that's very good!! thanks for info!
downgrade issue
hi, y just tried to upgrade my u8800 to 2.3 using the update from huawei but since the gps and de wifi didnt work I tried to downgrade back to 2.2, I dont really know if what I did was the right thing to do but I just copied the 2.2 dload folder to my sd card and tried to reinstall by presing the vol+vol-power keys and it seemed to work just fine, after it completed I just started the phone and it never woke up again it just vibrates a bit but nothing....does anyone know how can i fix it??it wont let me do anything the computer wont recognice it and there is no image at all....anyone please help me!!!
fermon797 said:
I just started the phone and it never woke up again it just vibrates a bit but nothing....does anyone know how can i fix it??it wont let me do anything the computer wont recognice it and there is no image at all....anyone please help me!!!
Click to expand...
Click to collapse
The decision to distort the battery. Insert, connect the USB to the phone (on the other end connected to a computer), press and hold keys + - food, and wait a few seconds, as soon as you see a red flashing light, unplug the data cable, you can start sewn.
Tnks!!
Igory0k said:
The decision to distort the battery. Insert, connect the USB to the phone (on the other end connected to a computer), press and hold keys + - food, and wait a few seconds, as soon as you see a red flashing light, unplug the data cable, you can start sewn.
Click to expand...
Click to collapse
Tnks!! im gonna try that but after doing that what should i do?? do i have to install 2.2 again??if so do i have to do this procedure with the sd card connected?? and also which rom would you recommend?? thank you so much for your answer!!!
fermon797 said:
Tnks!! im gonna try that but after doing that what should i do?? do i have to install 2.2 again??if so do i have to do this procedure with the sd card connected?? and also which rom would you recommend?? thank you so much for your answer!!!
Click to expand...
Click to collapse
Downgrade from 2.3.5 back to 2.2.2
U8800 V100R001C00B138SP04 (Overseas General) Android 2.2.2 from here
areedw said:
Hello, while I was testing 2.3.5 witch was great except that the mobile network was not woorking at all. So I decided that I needed too downgrade. And when I was browsing the phone I accidentally found this way.
This has not been proofed by anyone else I think.
Disclaimer: I do not take the resposibility for your device.
1. Put the dload on the root of SD-card (I used 138sp4)
2. Then go to storage in preferences. Head too the bottom then choose "upgrade SD-card". The phone blacked out, started up and installed 2.2
3. The phone boots up in recovery because of many errors. I choose wipe data/chache and wipe chache and reboot.
4. The phone rebooted and I am back to 2.2.2 from 2.3.5.
This method keeps the start-boot-picture (does not know if the other sulutions keeps it).
Sorry for my bad grammar on some of the words. I just wrote them down and did not have the time to fix them.
Click to expand...
Click to collapse
Yes its working great but if u have custom rom installed remember to factory reset, wipe cache and dalvik in recovery before downgrade, if u will not do this phone will stay at unpacking screen forever.
I was running virtuous primodonna. i wasnt doing anything, but my phone randomly illuminated with a black screen. i pulled the batter and when i rebooted it stayed at splash screen, then the screen showed random screwed up lines and all this. then it rebooted by itself and went to recovery. I've wiped my data and cache and dalvik but nothing works. i've tried restoring backups but it says that its failing to recover the system. please someone help
If no one knows. can someone please provide me with a rom that will brick my phone so it WONT BOOT UP WHATSOEVER. that way i can go to the tmo store for replacement? so they cant go into recovery and figure out i've rooted it. PLEASE someone
tradejak66 said:
I was running virtuous primodonna. i wasnt doing anything, but my phone randomly illuminated with a black screen. i pulled the batter and when i rebooted it stayed at splash screen, then the screen showed random screwed up lines and all this. then it rebooted by itself and went to recovery. I've wiped my data and cache and dalvik but nothing works. i've tried restoring backups but it says that its failing to recover the system. please someone help
If no one knows. can someone please provide me with a rom that will brick my phone so it WONT BOOT UP WHATSOEVER. that way i can go to the tmo store for replacement? so they cant go into recovery and figure out i've rooted it. PLEASE someone
Click to expand...
Click to collapse
Let's not brick your phone intentionally just yet! Try getting hold of a PD15IMG.zip (2.2.1 or 2.3.4, either works unless you want to root again, then go for 2.2.1). Boot into bootloader with the PD15IMG on the root of your SD, then let it update. If it doesn't and says Fail-PU, then you are bricked and could send it back to T-Mobile. Or you could try flashing another ROM. Hope this helps!
invasion2 said:
Let's not brick your phone intentionally just yet! Try getting hold of a PD15IMG.zip (2.2.1 or 2.3.4, either works unless you want to root again, then go for 2.2.1). Boot into bootloader with the PD15IMG on the root of your SD, then let it update. If it doesn't and says Fail-PU, then you are bricked and could send it back to T-Mobile. Or you could try flashing another ROM. Hope this helps!
Click to expand...
Click to collapse
tried that too..... and i dont want to send it back to t-mobile since they can still look and see its rooted. so yes thats why i need to brick it lol. please.
tradejak66 said:
tried that too..... and i dont want to send it back to t-mobile since they can still look and see its rooted. so yes thats why i need to brick it lol. please.
Click to expand...
Click to collapse
OK since that did not work, place the PD15IMG on your SD, and when it is updating, pull the battery. That will brick it for sure (I think..). Press thanks if I helped.
invasion2 said:
OK since that did not work, place the PD15IMG on your SD, and when it is updating, pull the battery. That will brick it for sure (I think..). Press thanks if I helped.
Click to expand...
Click to collapse
k hold up let me try
tradejak66 said:
I was running virtuous primodonna. i wasnt doing anything, but my phone randomly illuminated with a black screen. i pulled the batter and when i rebooted it stayed at splash screen, then the screen showed random screwed up lines and all this. then it rebooted by itself and went to recovery. I've wiped my data and cache and dalvik but nothing works. i've tried restoring backups but it says that its failing to recover the system. please someone help
If no one knows. can someone please provide me with a rom that will brick my phone so it WONT BOOT UP WHATSOEVER. that way i can go to the tmo store for replacement? so they cant go into recovery and figure out i've rooted it. PLEASE someone
Click to expand...
Click to collapse
do this: wipe data/factory reset
wipe cache
wipe dalvik
flash the original ROM (the one you have a backup of, but not the actual back up)
THEN restore the backup, it shouldnt get stuck at system anymore
i had a similar problem and this helped. hopefully it works for you
invasion2 said:
OK since that did not work, place the PD15IMG on your SD, and when it is updating, pull the battery. That will brick it for sure (I think..). Press thanks if I helped.
Click to expand...
Click to collapse
I've tried twice and it still boots :0
tradejak66 said:
I've tried twice and it still boots :0
Click to expand...
Click to collapse
Whoops. I think it's flashing a new radio then. Flash the radio just like you did with the PD15IMG and take the battery out during the process. If it still boots, I'll look into how to brick it lol!
invasion2 said:
Whoops. I think it's flashing a new radio then. Flash the radio just like you did with the PD15IMG and take the battery out during the process. If it still boots, I'll look into how to brick it lol!
Click to expand...
Click to collapse
lol. start looking now just in case.
invasion2 said:
Whoops. I think it's flashing a new radio then. Flash the radio just like you did with the PD15IMG and take the battery out during the process. If it still boots, I'll look into how to brick it lol!
Click to expand...
Click to collapse
I can't even access the recovery anymore. i have the PD15image thing pop up everytime so i cant get to the sd card whatsoever. i took out my sdcard then tried to access the recovery but it doesnt work
Actually, I think we've done a pretty successful job, because, they can't access the recovery, the PD15img keeps saying Fail-PU. the only thing left is S-Off, which i hope they dont notice >.>
tradejak66 said:
Actually, I think we've done a pretty successful job, because, they can't access the recovery, the PD15img keeps saying Fail-PU. the only thing left is S-Off, which i hope they dont notice >.>
Click to expand...
Click to collapse
I think you're fine honestly. Good luck matey!
Get a 12v power supply, cut the end off and strip the wires. Take the battery out and touch the wires to the phones battery contacts a couple times. Replace battery try to power on. If it doesn't turn on your done, if it does try again. Tell them it was on the charger and shut off when you unplugged it and wouldn't turn on.
Sent from my HTC Glacier using Tapatalk
tradejak66 said:
I can't even access the recovery anymore. i have the PD15image thing pop up everytime so i cant get to the sd card whatsoever. i took out my sdcard then tried to access the recovery but it doesnt work
Click to expand...
Click to collapse
I had a similar problem when the splash screen got stuck last night flashing a new radio. I took the sdcard and plugged it in the netbook, accessed the root rolder and renamed the PD15IMG.zip so the HBOOT wouldn't read the file. It stopped the HBOOT from reading the file so I could access Recovery then reflashed my recovery file. I forgot to do the data wipe/dalvik before I flashed the radio lol.
This is an AWESOME how to brick your phone on purpose guide good job guys
Sent from my ROOTIE TOOTIE FRESH 'N FRUITY GLACIER
OH GOD tmobile is out of MT4g's and i had to order one from HTC. they specificly stated they will make sure its not rooted and all that >.> I asked the woman what rooting was if that helped but obviously i dont think it will. Im pissed my pants when i heard that sentence. HTC is obviously more prone to finding root then T-mobile who will just throw the phone away 0_0
tradejak66 said:
OH GOD tmobile is out of MT4g's and i had to order one from HTC. they specificly stated they will make sure its not rooted and all that >.> I asked the woman what rooting was if that helped but obviously i dont think it will. Im pissed my pants when i heard that sentence. HTC is obviously more prone to finding root then T-mobile who will just throw the phone away 0_0
Click to expand...
Click to collapse
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
grimey01 said:
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
Click to expand...
Click to collapse
Where there's a will (and a hammer) there's a way.
grimey01 said:
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
Click to expand...
Click to collapse
Yea its hard to permabrick unless you don't want to brick it from what I hear...
Sent from my HTC Glacier
grimey01 said:
and then youre gonna be waiting another 2 months to recieve the replaced/repaired/refurbished phone..
you could have just made it work instead of completely bricking it
its an HTC android.. very, VERY hard to perma-brick
Click to expand...
Click to collapse
your assuming that it was software that broke >.> it was most likely hardware since it broke in this manner and no flashing, resets, anything helped. and its 2 weeks btw lol.
Dear All,
After losing my Samsung Galaxy Note in Amsterdam during a heavy weekend I am back on my girlfriend's old ZTE Blade and have been trying to update it a little.
I downloaded the KonstaKang ROM and GApps to the ext. Sd card and booted into clockwork mod recovery (I rooted and flashed a custom rom for her when I gave it to her originally).
I did the full wipe just to make it all as clean as poss and went to install the new rom but ran into some problems.
Firstly the sd card could not be accessed. It was if it was not mounted. I tried various things including mounting it in mounts and storage, restarting recovery, reformatting the sd in another android and the pc etc. Eventually (it felt random) it let me choose zip from sd.
Thats when the rom was selected but it then told me that the rom was (bad) and would not install. Again I redownloaded it and another rom and also a new version of cwm. Still nothing would work it was all (bad).
Out of frustration I kept trying and eventually it changed its mind and let me install the rom. After installation I attempted to reboot system but it just hanged at the boot logo and would go no further.
I have tried all the above multiple times and all combos of things I can think of to get it to work but no luck. The phone randomly seems to decide if the .zips are (bad) but at least it allows me to access them now. Ive also tried installing the other rom and new cwm but nothing will work. Boot logo and nothing more.
Anyone have any ideas what might be wrong? Whats the best way to get a rom on this old blade?!
Many thanks x
Sent from my GT-I9300 using Tapatalk 2
Well, first, you have an S3. Why use the Blade?
Second, have you looked into TPT + ROM? Also, what Gen blade is it? Once you can get something stable like cm7 booting, we can progress further
Sent from my Nexus 4
QuantumFoam said:
Well, first, you have an S3. Why use the Blade?
Second, have you looked into TPT + ROM? Also, what Gen blade is it? Once you can get something stable like cm7 booting, we can progress further
Sent from my Nexus 4
Click to expand...
Click to collapse
Well I believe it is a gen2 blade. I vaguely remember having to update it from gen1 but I cant be 100% sure. It was a long time ago!
I am using my girlfriends s3 to get on these forums so unfortunately I cant keep it!
I havent looked at tpt + rom and am unsure what that is at the moment . I shall have a read.
I must also say that I managed to install a new version of cwm but still no luck with any roms.
I am loading new roms on the ext sd from this s3 or through my pc I was wondering if the files were getting corrupted somehow. My pc doesnt see the phone so I have to use a card reader.
So yes roms are still saying 'cant open... (bad)' error when trying to install...
Thanks for your reply
Sent from my GT-I9300 using Tapatalk 2
rattymon said:
Out of frustration I kept trying and eventually it changed its mind and let me install the rom. After installation I attempted to reboot system but it just hanged at the boot logo
Click to expand...
Click to collapse
I also have realised since installing new version of cwm that it never actually let me install it just restarted recovery and didnt show the error log.
Sent from my GT-I9300 using Tapatalk 2