Related
I bought a Rogers HTC Magic for a pretty cheap price. It had The Rogers 1.5 Sense UI update on it. I decided I wanted to root it and load other ROMs, etc. So I read that the easiest method was to use Universal Androot to root it, and ROM Manager (from the Market) to flash the appropriate recovery image.
So, I installed both apps. I first ran Universal Androot and rooted. I confirmed root through ADB and also Super User permissions. I then restarted the phone just for peace of mind. After the restart, I ran ROM Manager. It automatically popped up and asked me if I was running an Ion/My Touch or an HTC Magic. I selected HTC Magic, because that's what this is. So then it flashed the recovery image and restarted the phone. When it restarted it went to the Rogers boot screen for a few seconds, and then started a loop of restarts. That's all it does now. It shows the Rogers screen for a few seconds, goes black and reboots over and over. I have tried booting into HBOOT, Fastboot, and into recovery. I cannot boot into any of them. One thing I did notice is that when I'm pressing any of the combinations (volume down + power, home + power, menu + power) for a very brief half a second right before the phone restarts, the bottom of the screen says "ClockwordMod ..." where ... is the version of the image (I'm at work without the phone, so I don't recall the exact number there).
So, is this thing officially a paperweight now, or is there some sort of hope?
Thanks.
Paul
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
adrift02 said:
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
Click to expand...
Click to collapse
Okay. That's weird. I mean, my phone is a Magic so choosing the option for the Magic instead of the Ion/MyTouch seemed to make sense.
Anyway, I cannot get anywhere. Holding vol+ and power does nothing, neither does home and power or back and power. Are there any other tricks to getting anywhere beyond this endless restart loop?
Thanks.
Starting to think I'm screwed.
PaulieORF said:
Starting to think I'm screwed.
Click to expand...
Click to collapse
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
ezterry said:
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
Click to expand...
Click to collapse
Thanks for the reply!
Right, I cannot get into fastboot or hboot. I'll try running the battery down when I get home today. Interesting idea.
Unfortunately running the battery dead with restarts didn't do the trick.
Any idea if there's any place I can send it to who has the smarts to jtag recover this thing?
Thanks.
me too
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
tmokeith said:
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
Click to expand...
Click to collapse
I don't think it's the same thing.
I rooted, loaded ROM Manager and installed the recovery. I was never even able to get into recovery in order to try to load any ROMs.
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
nate_benji said:
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
The phone does not identify itself to the computer, so this doesn't work.
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
nate_benji said:
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Oh yes. I've gone crazy trying every key combination with every combination of taking battery out, plugging it in, USB cable attached, detached, etc.
The phone never identifies itself as a piece of hardware to the computer in the 5 seconds between reboots.
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
naparstekk said:
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
Click to expand...
Click to collapse
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
I wasn't able to get hboot or fastboot. I pluged off and on the battery in the exact moment when the Logo came out after restarting. The logo was on the screen for the whole time, even while battery plugged off. I guess, i've done it so quickly that phone didn't switched off.
I think i was holding the power+home or power+back buttons all the time.
Can't really rember the exact way, sorry.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
Try removing the SD card and booting if its not restarting due to the wrong radio too soon that may help.. if you get into android restore the SD card and run the exploid process I posted a bit back for rogers magics, or the older goldcard method.
I've played around with taking the battery out and putting it right back in at all different times during the booting and can't get the phone to behave any differently. Iv'e tried it with SD card in and SD card out, USB cable in and USB cable out. I can't get anywhere.
I did notice that the phone does show up as an Android device for a second when it's booting. Tried to catch it in adb but no luck.
Starting to think this thing is shot. Any other ideas?
Just so everyone can see what's happening, I recorded a video and uploaded it. Linked below:
http://www.youtube.com/watch?v=hPoxMzm0MVU&hd=1
try to hold and KEEP holding the back + power... Not volume down!
Don't push and release like you did in the video.
Galaxy S i9000 (Bell Mobility) wont start. Rooted with LagFix.
HELP!!! I cant get anywhere. Can anyone solve this
What happens: it starts up with logo and sound and then to a black screen. Any attempts end up with the same result
What I did prior:
1 installed CacheMate for Root Users and busybox
2 tried CacheMate for Root Users (didnt want it)
3 uninstalled busybox (when I installed, I noticed it showed 2 other versions installed. I searched and manually deleted them)
4 phone shut off unexpectedly
How I tried to fix:
1 tried to reboot
2 pulled battery tried reboot
3 pulled sd card tried reboot
4 pulled sim/sdcard tried reboot
5 vol+ home pwr
6 vol- home pwr
7 pwr menu
8 even tried heat up trick in desperation
vol+/vol- + home + pwr are disabled
can't restart to apply 3 button fix > can't get into recovery > can't reflash without 3 button recovery
do you remember if the USB debug mode is enabled or disabled?
if it's enabled, then you can let it boot and do the
adb reboot recovery
or
adb reboot download
if that doesn't work the only way to fix is to send it back to the store for repair
If it goes to the Logo screen, then when it goes black if the back and home buttons still light up your internal sd card has crashed and you need to send it in for repair at bell
bigc_13 said:
If it goes to the Logo screen, then when it goes black if the back and home buttons still light up your internal sd card has crashed and you need to send it in for repair at bell
Click to expand...
Click to collapse
This. Been there, done that, wrote the book. Me and my buddy. Stock too.
Sent from my GT-I9000M using XDA App
It's bricked... internal SD is fried.
To confirm, if you can get into Upload Mode, flash a 2.2 ROM, which will give you the ability to get into Recovery mode... once in recovery mode, it will show you the Internal SD error that I'm talking about...
Take it back to the store before your 30 days are up - no use trying to waste time fixing it...
Happened to me as well. I was on my 10th+ firmware flash. Went to JPD or whichever 2.2 came right after JPC. I install RyanZa's OCLF and within one hour it crashed and wouldn't boot.
I was able to run JM8 or any 2.1 Firmware but without Internal SD. I was just running off the internal 2gb partition that it created off the external SD when it can't find the internal SD. Thats why when the internal SD is corrupt, the phone won't boot into android without the external SD installed.
In the end it was 2 days before my 30day replacement, so I took it to bell and had it replaced.
Running stock update 1 for bell (JH2) with Voodoo 4 on current replacement.
Hey, I also have this problem. I originally bought it semi bricked. The phone was not even showing the boot screen, but I managed to flash so now it does the above.
What are mu options here. Im not a Bell Client so they won't give me a replacement. I'd prefer not to spend money sending it in, but will if i have to. But i doubt that bell would take it in even if I did pay because im not their customer...Telus obviously doesn't support the Galaxy so I can't go to them either.
How were you able to get it running off your memory card? I don't mind doing that actually!
I had this happen to me once before and and i did a factory reset and i worked perfectly! and now its happened again and i believe my internal sd is fried! kinda really sucks
Kendren said:
Hey, I also have this problem. I originally bought it semi bricked. The phone was not even showing the boot screen, but I managed to flash so now it does the above.
What are mu options here.
Click to expand...
Click to collapse
Call samsung direct.
1-888-751-4078 (i'm assuming your in canada) and send it in.
I installed the latest build of Cyanogen Mod 7 on MyTouch 4G, and everything went smoothly, but now my phone won't turn on at all. Nothing happens when I hit the power button. Not even a splash screen which I thought was weird. I have a recovery file, but if I can't access the bootloader/recovery screen, can't really recover it.
Any suggestions? I luckily have a backup Windows phone 7 near me (HD2), but I'm just wondering if the MyTouch 4G can be recovered.
Thanks!
Edit: Also note, that I can't do anything, including hboot, fboot, get anywhere. It will not power on, and looks like it won't recharge as well.
Edit #2: Uh..looks like taking out the Sim Card worked.
Have you try pressing volume key down and power at the same time to get into Hboot then scroll down into recovery and wipe
Sent from my HTC Glacier using XDA App
For the longest time, I couldn't power it up until I took out the sim card. Which I finally figured out. I'm doing the wipe right now, thankfully. I'm trying to figure out now what I did wrong...
Thats gotta be scary im running cm7 now had no problems flashing any of the builds knock on wood lol
Sent from my HTC Glacier using XDA App
this happened to me earlier when i pushed/flashed/installed (whats the correct term here?) CM 6.1.2 on to my phone. i thought i did it right then i went to reboot and it just shut off. wouldnt turn on or anything. thought i ****ed up and bricked it. after taking battery/sd card/sim card out it worked though.
it was SO relieving.
Is CM7 not stable?
Battery Pull
All you have to do is a batt pull (no sim or ext. sd) and go into H Boot ( Hold bottom volume buttton and then power on button & hold until you see letters and release both buttons and you will be in H Boot) then hit recovery. If that doesnt work and your flash screen is stuck, go back to H Boot, hit recovery...wait for green letters up top, go down to backup and restore then hit restore.
I have the same problem
I tried to Flash the cyanogen mod, i followed the prompts i click the button where its supposed to go into recovery, then completely blank screen. I left it for 15 minutes then took the battery in then out but now it won't power on and shows no sign of life. PLEASE HELP ME. the sim card thing doesn't seem to work for me.
HELPMEPLEASE!!! said:
I tried to Flash the cyanogen mod, i followed the prompts i click the button where its supposed to go into recovery, then completely blank screen. I left it for 15 minutes then took the battery in then out but now it won't power on and shows no sign of life. PLEASE HELP ME. the sim card thing doesn't seem to work for me.
Click to expand...
Click to collapse
Does the LED show when you connect the phone to a power source? Can adb see your phone?
Sent from the HTC Glacier Sense 3.0 using XDA premium app
saranhai said:
Does the LED show when you connect the phone to a power source? Can adb see your phone?
Sent from the HTC Glacier Sense 3.0 using XDA premium app
Click to expand...
Click to collapse
No, it doesn't power on or show the LED screen at all.
And also doesn't show up on ADB.
wrong recovery image
If you are flashing cyanogen 6, use clockworkmod 2..x. If you are flashing cyanogen 7, use clockworkmod 3..x
Not sure why some roms don't work on clockwork mod 2..x.... Maybe a limitation in a past clockworkmod which was fixed in a later version.
xmc wildchild22 said:
If you are flashing cyanogen 6, use clockworkmod 2..x. If you are flashing cyanogen 7, use clockworkmod 3..x
Not sure why some roms don't work on clockwork mod 2..x.... Maybe a limitation in a past clockworkmod which was fixed in a later version.
Click to expand...
Click to collapse
it's because clockworkmod recovery 2.x only flashes up to ext3 filesystems. the new clockworkmod recoveries, anything above v3.x has support for both ext3 and 4 filesystems. since cyanogenmod 7 has an ext 4 filesystem, the ROM will not flash correctly on clockworkmod 2.x.
1st of all i want to apologize for my bad english .
Few hours ago i had installed this rom, it was just fine, until i applied the app2sd option from SupSetupV16 application. After that my phone turned off with no reason and from then it restarts again and again. I've tried with an sdcard with ext3 & fat32 partition (cuz the app2sd option in this rom requires it, but i didn't saw it earlier, and my phone has no s-off) and the phone loaded the start animation of the rom, than turned off and all over again. The battery level was almost 50% just before the 1st restart, and now the phone is in the charger. The phone does not receive any command from the hardware buttons, just cant enter the recovery mode .. i feel rly fckd up. No volume up + power, volume down, back + power .. nothing. I'll charge it all night and try again in the morning. Somehow im smelling the service ...
i think you got loop because the phone is reading wrong data.
ok... do you have ClockworkMod backup your stuff already? you can unplug your phone from the usb, if it have been boot loop from just now. poor phone. you can disconnect it from the battery. now its totally off. hold Vol - and power on your device. then on the menu, go to recover... the red [!] screen... From what i've know, i can only go to recovery using these combination from the phone is in OFF state. not while its loop booting, and it is somewhat safe to remove your battery when the phone is not writing something to the internal memory.
if you have ClockworkMod, you can run the update.zip (the fake Flash) or if you have hack4Legend (cant remember if this the name on the pc download as i dont use this anymore) plug in your usb to the pc and run Recovery.bat if your windows.
then your on ClockworkMod. from here onward i guess you know what to do. go flash a new rom or do a wipe the data and stuff to see of the loop stops.
hope this worked for you as this is what i did... for a few times already.
If this dont work for you. then you should try the search button for boot loop.
Oh, man .. u're awesome. On turned off phone .. volume - and than power is working fine and the fastboot menu appears. You're awesome, again! Thanks alot!
I think it's very hard to actually brick a HTC Legend... I've had this problem too and some other black screen problems. All could be solved!
Lol, I think as android are hard to kill. Really... not just our legend. But rest too.... I personally poisoned my friends to get android phones so that I get to play with them. Showing them how much these phone can do... and if you root them youll get more cool stuff! lol..
But, anyway. I'm glad it workd for you.
Sent from my Legend using XDA App
However with S-ON legend to have app2sd with superginger you have to apply before the overlay, reboot and then app2sd.
Sent from my Legend using XDA App
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much