Well, i've flashed my Blade with ColdFusionX ROM and everything seems to be great.
Then i decided to restart it and it stays on boot loop. It can be solved by entering on recovery and wiping the Dalvik Cache, but i want to know if there is another way to solve it? It's kinda annoying making it everytime i need to restart or shutdown.
Another question is for a good app to make USB Thetering, since the one on this ROM works but drains battery faster then USB provides.
Thanks and sorry about the bad english.
link to ROM's page: http://forum.xda-developers.com/showthread.php?t=1429539
Update:
Now things are worst then ever. I've updated ROM Manager to last version and then i can't enter on recover anymore and cellphone can't start.
Is there any way to flash the recovery from outside the phone?
Method 2.
http://www.modaco.com/topic/343587-guide-de-bricking-a-zte-blade/
Sent from my GT-I9300 using xda premium
Do you have Blade drivers for Windows 8, that drivers are for 7 and they aren't working.
Tryed method 2 but it didn't work, adb can't see my device connected. Now i'm trying method 3.
How can I know what TPT should i use?
Sorry for being so noob.
If you got your phone with 2.1 it is gen1, if 2.2 it is gen2.
Therefore, use gen2.
Sent from my GT-I9300 using xda premium
UrbanDrawer said:
If you got your phone with 2.1 it is gen1, if 2.2 it is gen2.
Therefore, use gen2.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
It is with 4.0.4 gen2, but i don't know if i have to use chinese or european TPT.
It was manufactured in china, so I use the Chinese TPT, right? Seems obvious but i'm kinda scared.
Update: Problem Solved!
I turned it in recovery mode, and it got stuck as was happening before. So I left it a while and when i plugged him on the computer, adb recognized it and I could use the fastboot of method 2.
But i still got the problem with the Boot-looping on ColdFusionX that I said on first post. Is there a way to fix this? (It can be fixed wiping the Dalvik Cache every boot, but it is annoying)
Flash another rom.
Sent from my GT-I9300 using xda premium
vittal said:
Update: Problem Solved!
I turned it in recovery mode, and it got stuck as was happening before. So I left it a while and when i plugged him on the computer, adb recognized it and I could use the fastboot of method 2.
But i still got the problem with the Boot-looping on ColdFusionX that I said on first post. Is there a way to fix this? (It can be fixed wiping the Dalvik Cache every boot, but it is annoying)
Click to expand...
Click to collapse
This will keep on happening because the rom u are using has stopped development. Soon u will also loose Google play.
Do what urbandriver said. I recommended konsta T' cm9 (Google it).
Sent from my Blade using xda app-developers app
Related
Hey guys!
Today when i was updating to CM9 my phone started bootlooping, and the big problem is that i can't get into recovery mode by using the 3 button combo.. But I can get into downloading mode, but my computer doesn't find my phone.
I'm really out of ideas here, help is much appreciated.
Edit: I followed step by step in CM9 thread http://forum.xda-developers.com/showthread.php?t=1592131
/Korhonen
korhonen said:
But I can get into downloading mode, but my computer doesn't find my phone.
Click to expand...
Click to collapse
Had similar situation day before yesterday .after hours od checking one after the other traced it to one missing pin in the USB cable (either burned out or rolled in on the micro usb plug) ..can also happen on the phone usb slot end. ( as one other person had experienced on this forum)
xsenman said:
Had similar situation day before yesterday .after hours od checking one after the other traced it to one missing pin in the USB cable (either burned out or rolled in on the micro usb plug) ..can also happen on the phone usb slot end. ( as one other person had experienced on this forum)
Click to expand...
Click to collapse
Hmm, I can hear the phone connect to windows though, and I had it connected just before I flashed the CM9. As the bootloop appeared so did the cpu not recognizing part :/
korhonen said:
Hmm, I can hear the phone connect to windows though, and I had it connected just before I flashed the CM9. As the bootloop appeared so did the cpu not recognizing part :/
Click to expand...
Click to collapse
try reboot your PC and phone
xsenman said:
try reboot your PC and phone
Click to expand...
Click to collapse
I tried that, no difference
korhonen said:
I tried that, no difference
Click to expand...
Click to collapse
Have you uninstalled and reinstalled drivers/tried different ones?
Sent from my GT-I9000 using xda premium
slaphead20 said:
Have you uninstalled and reinstalled drivers/tried different ones?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Ye, same. I've tried connecting other phones to the computer with the same cable and it works. So it's certain that the problem lies with the phone.
korhonen said:
Ye, same. I've tried connecting other phones to the computer with the same cable and it works. So it's certain that the problem lies with the phone.
Click to expand...
Click to collapse
Check the usb port and make sure pins are as they should be
Sent from my GT-I9000 using xda premium
Remove your micro sd, you should be able to get back in to recovery then. Once there, repeat flashing process including wipes. Should be okay then.
Just flash semaphore or any other ICS-Root Kernel with CWM for I9000 via ODIN and you should be fine (booting and getting CW back).
Instructions:
Download ODIN (if you don't have already)
Flash Kernel .tar package (don't check repartition!)
If you have never flashed with ODIN before I suggest you find a quick tutorial before you go to work.
Good luck!
Had your problem to, but not with cm9, i flashed it back to stock, then rooted and then updated it, seemed to work for me
Sent from my GT-I9000 using XDA
It's most certainly a driver issue. Uninstall the Samsung drivers and then reinstall them again.
If that fails, use this
http://www.4shared.com/office/ewdIWux2/usb-connection-issues-mtp-devi.html
to fix the MTP issue
superkoal said:
Just flash semaphore or any other ICS-Root Kernel with CWM for I9000 via ODIN and you should be fine (booting and getting CW back).
Instructions:
Download ODIN (if you don't have already)
Flash Kernel .tar package (don't check repartition!)
If you have never flashed with ODIN before I suggest you find a quick tutorial before you go to work.
Good luck!
Click to expand...
Click to collapse
You were right! Thanks alot! Thought I was doomed, but now it works.
A nooby mistake of me, it was the USB-drivers... Thanks for all answers and suggestions!
/Korhonen
One question...
Was it the driver issue or was it an issue with Odin?
TVwithParents said:
One question...
Was it the driver issue or was it an issue with Odin?
Click to expand...
Click to collapse
It was the drivers.
This seems like an appropriate place for a question.
I've been using the guide here:
theandroidsoul.com/cyanogenmod-9-cm9-nightly-rom-for-galaxy-s-installation-guide/
To try to install CM9. Using Odin I've flashed:
JW4_JW4_JW4.tar (worked)
CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.tar (worked)
Then I've stuck
cm-9-20120623-NIGHTLY-galaxysmtd.zip
gapps-ics-20120429-signed.zip
into the root directory, booted into recovery and tried to run the first zip.
Every time I do this it gets maybe 3 seconds into the install, and reboots. It then shows the "Galaxy S" logo, then "Galaxy S - Cyanogen" (some graphic with Cyanogen in the name) and flips to what looks like the installation text for two seconds - and then reboots and repeats.
I can't drop it back into recovery but I can force it into download mode and flash JW4 again and repeat from the top. This has happened a few times now and I always end up in the same place, which suggests I'm doing something wrong. Please fix my idiocy.
Having taken the time to read this
http://forum.xda-developers.com/showthread.php?p=24673062
....on your behalf I notice you have omitted certain steps, please read yourself to find the missing link
Sent from my GT-I9000 using xda premium
slaphead20 said:
Having taken the time to read this
http://forum.xda-developers.com/showthread.php?p=24673062
....on your behalf I notice you have omitted certain steps, please read yourself to find the missing link
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
No, I read that for one of the three times I tried. I assume I missed something?
1. Root your device and install ClockworkMod Recovery. - Covered by flashing CF Root, yes?
2. Reboot into Recovery using 3-button-combo
3. Do a Nandroid backup!
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the ROM from internal sdcard using ClockworkMod Recovery - Breaks here.
Click to expand...
Click to collapse
I did not do a nandroid backup though. Can that actually cause an issue?
OckyFlam said:
No, I read that for one of the three times I tried. I assume I missed something?
I did not do a nandroid backup though. Can that actually cause an issue?
Click to expand...
Click to collapse
Did you do the wipe/factory reset and wipe cache stage
Sent from my GT-I9000 using xda premium
slaphead20 said:
Did you do the wipe/factory reset and wipe cache stage
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Yes, definitely. It was in that link in my post and in the link you provided so I assumed it was important
Ive got a fairly new (old stock!) Blade that I have flashed using Swedish Snow RLS7 which has been working fine...no problems.
This week I turned the phone on and it gets as far as the Android boot screen (green robot, but NOT as far as the boot animation) and then reboots.
I *can* get in to Clockwork and have tried wiping all settings and reflashing the ROM. These processes all complete successfully, but the phone still does the same reboot cycle.
Any ideas what the problem might be here?
thanks
mike
Have you tried reflashing the recovery?
Here's latest cwm flashable zip : http://www.mediafire.com/?v3w87u6ua1cyui8
Sent from my GT-I9300 using xda premium
UrbanDrawer said:
Have you tried reflashing the recovery?
Here's latest cwm flashable zip :
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. I reflashed to the latest recovery and tried a different ROM. Unfortunately I get the same problem.....green Android boot logo which appears for about 20s, distortion/flickering at the end of this period and then a reboot. Recovery works fine.
I'm wondering if this is somehow graphics related......
I don't really think that it's graphic-related. I've had very similiar problem with my Blade, fixed it with this.
http://www.modaco.com/topic/343587-guide-de-bricking-a-zte-blade/
Sent from my GT-I9300 using xda premium
Hi Guys
I installed the official Gingerbread that is available from the Huawei site. Install was successful however phone boots fine for the first time but once i reboot it I am stuck in boot loop on Huawei logo. Recovery is reset to default so cannot flash anything that way.
I cannot root the phone via SuperOneClick as it needs logging switched on (Requires reboot).
When I access pink screen no drive is mounted in windows.
How can i remedy this problem?
Hi, try to wipe data and cache in recovery.
Sent from my U8800 using xda app-developers app
Ax1qwer said:
Hi, try to wipe data and cache in recovery.
Sent from my U8800 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply, when i wipe data and cache it boots fine for the first time but when i reboot It loads the OS but there are many force close errors then it reboots itself and goes into logo boot loop.
Do you have a repartition data?
scux said:
Do you have a repartition data?
Click to expand...
Click to collapse
I ended up going back to 2.2 and it has been stable, have got it rooted and am in the process of fixing recovery.
scux said:
Do you have a repartition data?
Click to expand...
Click to collapse
How do i get this?
jo3fis said:
How do i get this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2264426
Thanks Ax1qwer, didnt see your post until i had begun following the below
http://forum.xda-developers.com/showthread.php?t=1971266
Currently still doing it so will let you know how it goes.
A bit late but thought i better update.
The above worked perfectly and got my phone back up and running again as it was in a sad state . Only downside is my MAC and IMEI are now different which I have still yet to attempt the proposed fix below.
http://forum.xda-developers.com/showthread.php?t=2546063
I'm here to say thanks to scux,jo3fis,Ax1qwer. I had the same problem as jo3fis and i fixed it by going back to stock partition and then flashing gingerbread 2.3 518. Thank you all!
I installed the HORSEMAGEDDON ROM and it worked - for the most part. But it kept giving me annoying errors about different apps that were attempting to update every time I turned it on. So I tried to restore my backup that I had made with CWM 6.0.2.8. However the backup apparently did not restore properly because it now boot loops back into CWM any time I try to start it. I get the errors:
E:Can't open cache/recovery/log
E:Can't open cache/recovery/log
E:Can't open cache/recovery/last_log
E:Can't open cache/recovery/last_log
So I tried to reflash HORSEMAGEDDON but it still loops back into the CWM recovery screen.
I have wiped everything according to the instructions on the HORSEMAGEDDON thread.
HELP!! This happened to me on another U8800-51 phone and I wound up hard bricking it trying to get back to stock.
Anybody???
Does anybody have any ideas on how I can fix this?
Did you wipe cache/dalvik cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
iheartsamsung said:
Did you wipe cache/dalvik cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes. I did a wipe of data and factory reset as well.
What I would do is get an SD card with a custom rom on it and try installing it from recovery menu
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Obviously you have been having problems with that rom, so go with something different.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
iheartsamsung said:
Obviously you have been having problems with that rom, so go with something different.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Okay. Here is what I did step by step:
1. I was on Stock 2.2.2 Froyo and flashed HORSEMAGEDDON successfully. But I had some errors related to updates since it was such an old ROM the updates were all for much newer versions of the apps tied to 4.x.x.
2. I attempted to restore my backup made with CWM 6 to return to the stock. It said it completed successfully but when I rebooted it just looped into the recovery screen with the error messages posted in my first post.
3. So I tried to reflash HORSEMAGEDDON and it said it completed successfully. But it still bootloops into recovery.
4. I can access most of the features of the recovery. I can access the pink screen and swap recovery versions. I can access my SD card from my PC when I mount it from recovery.
5. Yes, I did do full wipes with each attempt to reflash.
The ROM was not the problem. It worked and worked well other than update issues for apps. It was only after attempting to restore to stock I ran into issues.
The problem appears to be something was corrupted when I tried to restore my backup, even though it said it completed successfully.
So if I try to flash yet another custom ROM, even if I could find one I trust given all of the version issues etc., I don't think it would act any differently. But if somebody can recommend one I am all ears. Keep in mind I have a -51 phone so it will have to be for that or the PRO.
Given that, how can I get back to stock? Am I the only person who has ever had this problem? I don't believe that is the case, so somebody must know how to fix it or can point me to a procedure to repair the internal memory.
Help!!
I'm new at xda so it's not letting me post an external link. Google "bootlooping" and the first one in list is from xda, just follow the instructions
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks but.....
iheartsamsung said:
I'm new at xda so it's not letting me post an external link. Google "bootlooping" and the first one in list is from xda, just follow the instructions
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
None of the fixes on this link seem to apply to my situation.
When I said "bootloop" I may have misused the term. What happens is I power up, it goes to logo screen for about 10 seconds, shuts down and restarts to logo screen then goes into recovery after about 5 seconds. From other info that I have found it is due to a corrupt bootloader and I need to reflash the bootloader. Problem is, reflashing the bootloader i.e. CWM, does no good at all.
I am also hampered by lack of info specific to the -51 model. And I cannot find a copy of the stock ROM anywhere that is for the -51.
So essentially I am screwed. All of that said, I have found a new phone for $40.00 so all is not lost. It's a U8800 but not the -51 or PRO. I don't plan on customizing it, I'll just stick with stock. After trashing two phones even after following the advice to "BACKUP" I think enough is enough. Backing up did me no good whatsoever in both cases.
In my estimation, the culprit is CWM, or at least the versions I used.
If anybody has any advice I'm all ears.
Hi guys, I made a mess today. I decided to restore my stock LG software backup and everything went well. Then there were some LG updates and when they downloaded, I chose to install them. That took me to TWRP. I figured it needs the stock recovery to install the updates so I gave up on the updates and tried to reboot my device. It booted back to TWRP. I found it a bit weird, but I didn't care since I had a backup on the phone. I wiped data, cache, system and dalvik and restored the backup. Guess what, the phone would still only boot into recovery. I started freaking out so I wiped everything except internal again and flashed an AOSP based rom along with the gapps. Still wouldn't boot except recovery. Then I started to freak out even more and decided to wipe EVERYTHING, along with Internal storage. And here I am now, wiped every single thing on the device, stuck in recovery and can't connect my phone to the PC with usb. just a few minutes before I have to leave home. Any ideas on how to fix this? It was just some pointless LG update and it caused such a mess... ADB sideload won't work for me, I'm gonna attempt to find some drivers or something.
Anybody?
Sent from my HTC One X using xda app-developers app
Evetything you need its allready posted. Just search
Sent from my LG-D802 using Tapatalk
darkobas said:
Evetything you need its allready posted. Just search
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Dude, I've done my research and tried to fix it myself. The phone won't go into download mode and it won't connect to my PC. Drivers installed, LG tool installed. I just don't know what to do and I need help from someone who does know.
ViktorN said:
Dude, I've done my research and tried to fix it myself. The phone won't go into download mode and it won't connect to my PC. Drivers installed, LG tool installed. I just don't know what to do and I need help from someone who does know.
Click to expand...
Click to collapse
If you have twrp 2.6.3.4 you sideload rom but this may not help you.
You are going to have to go back to 100%stock.
Sent from my LG-LS980 using xda premium
mchlbenner said:
If you have twrp 2.6.3.4 you sideload rom but this may not help you.
You are going to have to go back to 100%stock.
Sent from my LG-LS980 using xda premium
Click to expand...
Click to collapse
Sideloading won't work for me either.
Sent from my HTC One X using xda app-developers app
In TWRP you have USB-OTG. If you have this cable you can install ROM from USB-flash)
I had the same issue. Only way to fix it was with the LG flashing tool. Make sure the usb port you are using on your computer is working and the cable isn't broken. I just followed the steps from this thread and it worked 100% for me.
http://forum.xda-developers.com/showthread.php?t=2432476