So here's what happened. I installed MaximusHD and it works fine. But now im looking to upgrade to 4.4, so i tried flashing a 4.4 rom, and the recovery gives me errors. So i tried the red dragon elite method to fix my SD card. All i did was plug in my phone and flash stock recovery and then CWM again.
Thats when a new, very troublesome method started. When I'm in my recovery my computer says that my sdcard only has 48 megabytes free, but when i boot into android my computer says there's 11 Gigabytes free. Also I've noticed that there was a completely different list of folders when I'm in recovery.
When boot into android my phone shows normal folders (Android, Music, Media, all the usual stuff). But once im in recovery, all it shows is clockworkmod and my SD is only 48MB
I've also tried TWRP and CWM with no luck. Please help, I'm stuck on Maximus :crying:
XxbloodxrushxX said:
So here's what happened. I installed MaximusHD and it works fine. But now im looking to upgrade to 4.4, so i tried flashing a 4.4 rom, and the recovery gives me errors. So i tried the red dragon elite method to fix my SD card. All i did was plug in my phone and flash stock recovery and then CWM again.
Thats when a new, very troublesome method started. When I'm in my recovery my computer says that my sdcard only has 48 megabytes free, but when i boot into android my computer says there's 11 Gigabytes free. Also I've noticed that there was a completely different list of folders when I'm in recovery.
When boot into android my phone shows normal folders (Android, Music, Media, all the usual stuff). But once im in recovery, all it shows is clockworkmod and my SD is only 48MB
I've also tried TWRP and CWM with no luck. Please help, I'm stuck on Maximus :crying:
Click to expand...
Click to collapse
I take it you are s-off already?
What 4.4 rom are you trying to flash?
When you are flashing the 4.4 rom, what goes wrong? Do you successfully flash the rom and go into a bootloop or do you not manage to flash the rom at all?
Can you post a screenshot of what your computer sees when you are in recovery?
Also can you post a picture or type up of your white bootloader screen, if you're not sure what i mean, mine starts by saying:
tampered
unlocked
vle pvt ship s-off rl
tomk11 said:
I take it you are s-off already?
What 4.4 rom are you trying to flash?
When you are flashing the 4.4 rom, what goes wrong? Do you successfully flash the rom and go into a bootloop or do you not manage to flash the rom at all?
Can you post a screenshot of what your computer sees when you are in recovery?
Also can you post a picture or type up of your white bootloader screen, if you're not sure what i mean, mine starts by saying:
tampered
unlocked
vle pvt ship s-off rl
Click to expand...
Click to collapse
I've attached the screenshots, a big problem is in recovery it shows different files versus when its booted into OS.
In recovery it says 48MB free and shows /sdcard -> TWRP. thats it. and /internal_sdcard is blank.
but when i boot into OS i have 12GB free and i see normal folders like Downloads, music, media, etc.
XxbloodxrushxX said:
So here's what happened. I installed MaximusHD and it works fine. But now im looking to upgrade to 4.4, so i tried flashing a 4.4 rom, and the recovery gives me errors. So i tried the red dragon elite method to fix my SD card. All i did was plug in my phone and flash stock recovery and then CWM again.
Thats when a new, very troublesome method started. When I'm in my recovery my computer says that my sdcard only has 48 megabytes free, but when i boot into android my computer says there's 11 Gigabytes free. Also I've noticed that there was a completely different list of folders when I'm in recovery.
When boot into android my phone shows normal folders (Android, Music, Media, all the usual stuff). But once im in recovery, all it shows is clockworkmod and my SD is only 48MB
I've also tried TWRP and CWM with no luck. Please help, I'm stuck on Maximus :crying:
Click to expand...
Click to collapse
just FYI, you need to use the TWRP recovery posted in the original post of the Maximus thread. Any other version of TWRP or CWM will not work.
tivofool said:
just FYI, you need to use the TWRP recovery posted in the original post of the Maximus thread. Any other version of TWRP or CWM will not work.
Click to expand...
Click to collapse
Thank you so much! this fixed my problem! :laugh:
Related
hello, I have a problem with a desire s phone which keeps booting into recovery mode when i turn it on. here's my step by step of what I did that got me into this predicament.
the phone had a stock 1.48 asia rom 0.98.0002 bootloader locked, and unrooted. so first I ran revolutionary had no problems there, had a revolutionary logo on my bootloader afterwards and the bootloader version was now 6.98.0002 or something I forget. anyway the next thing i did was I downloaded the stock euro rom 2.10.401.9 and extracted the rom.zip then renamed it to PG88img.zip copied it to the memcard ran fastboot, then fastboot automatically installed the zip after installation restarted the phone, now the phone was stuck on the white htc screen, so I ran recovery press the power and vol up and did a factory reset, had no luck with it still stuck on htc screen, now after reading a lot of threads, downloaded the ENGpg88img bootloader flashed it using fastboot and it was successful, the revolutionary logo was gone and the bootloader was now 6.98.0000 ( PG880000) but now when I rebooted the phone it would go directly back to recovery!! So the next thing i did was ran the euro rom again from the memcard thru fastboot and it updated the bootloader to the newest version and had a "locked"on top of the screen, so i did a boot unlock using htcdev and now its unlocked, then downloaded the clockwork recovery for saga then flashed it using fastboot with no problems. so now when I turn on the phone it goes straight to clockwork recovery! So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
long story short, I can only use fastboot, and if I use clockwork mod recovery to mount system i can do some adb commands. i also tried putting it in fastboot and ran an official RUu but I always get error 150. any help would be greatly appreciated.
It seems that your chip is gone. I have the same problem (boot looping) and had to try reclamation by phone provider. Find thread with "boot looping", or "white screen". You will find some software for a searching of your chip. Finaly all depends on your mobile vendor
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Could you tell us how you solved it?
batmite said:
yeah i thought it was the chip, but after 3 days of tinkering with it and reading a lot of threads i finally got everything back to normal. thanks for replying though zdech
Click to expand...
Click to collapse
Hi, I have the same problem with HTC Desire.
Could you tell how you solved this please?
I don't know if he did what he wrote, but a big mistake was the last step.
batmite said:
So last thing I did which also failed was I downloaded a pre rooted stock rom euro 2.10, placed it on memcard installed the zip from clockwork recovery then wiped all the data, dalvik cached and all then rebooted. But it still went back to clockwork recovery now I'm stumped. Really need help on this one.
Click to expand...
Click to collapse
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Sent by my fingers to your head.
eyahl said:
I don't know if he did what he wrote, but a big mistake was the last step.
he installed ROM and wiped afterwards. Of course it fails at booting ;-)
If you really are in the same situation like him, wiping first and install ROM afterwards should solve the problem ;-)
Click to expand...
Click to collapse
Have to disagree with you there, what he said was
installed ROM
wiped DATA
wiped CACHE
rebooted
The ROM ZIP would have been flashed into SYSTEM not DATA, so wipe shouldn't have caused a problem
question is did BOOT flash ok?
I have a 2.2.0 hboot 1.14 unlocked, tampered CID1111111 One XL from AT&T. I was trying to try my first cooked ROM Friday night and I think I may have totally screwed up. I did a "factory reset" from the bootloader instead of from TWRP 2.3.1. My phone gets to "initiating Swagger" and gets stuck. I tried to re-ROM but TWRP can't find the directory. Everything appears to have been over-written. I tried to use the 2.2.0 RUU to start over, but now my computer doesn't recognize the device in HTCsync. I tried to re-image the hboot with a stock 2.2.0 image to see if that would at least start up so that I could use the RUU. It doesn't appear to have helped. HTCsync still doesn't recognize my phone although it now alerts me that the device "MyHTC" is now on the computer. I tried to mount the USB with TWRP and the computer tells me that the drive is "unformatted" and asks to "format?" So far I've cancelled out of that.
Is this device borked beyond repair?
Update: The solution was very sinple. Reformatted SD in FAT32. Re-downloaded AOKP and Gapps. Extracted the boot.img file from AOKP. Copied zipped AOKP and Gaaps to newly formatted SD. Flashed the boot.img file in fastboot using the Team Nocturnal tool. Everything booted normally and runs great!
Many thanks to area51avenger and crappyvate!! You guys are what makes this community rock! Keep up the good work.
I believe I had this problem yesterday when trying to install AOKP, I didn't flash the boot.img before I ran the .zip in TWRP. I was stuck in the boot screen and then wiped all my data. Couldn't mount SD from TWRP, had to install HTCSync on my computer, relock the bootloader, and run the RUU of what I was previously on. I tried to go to 1.85, but it didn't allow me because I was previously on 2.20, getting the RUU for 2.20 and running it gave me back stock Sense, and I re-unlocked my bootloader and was able to successfully install AOKP after flashing the boot.img.
Don't factory reset from bootloader.
Format card to fat32, mount usb storage in twrp, copy aokp over.
Install as per the 1000 threads here
sdimock said:
I have a 2.2.0 hboot 1.14 unlocked, tampered CID1111111 One XL from AT&T. I was trying to try my first cooked ROM Friday night and I think I may have totally screwed up. I did a "factory reset" from the bootloader instead of from TWRP 2.3.1. My phone gets to "initiating Swagger" and gets stuck. I tried to re-ROM but TWRP can't find the directory. Everything appears to have been over-written. I tried to use the 2.2.0 RUU to start over, but now my computer doesn't recognize the device in HTCsync. I tried to re-image the hboot with a stock 2.2.0 image to see if that would at least start up so that I could use the RUU. It doesn't appear to have helped. HTCsync still doesn't recognize my phone although it now alerts me that the device "MyHTC" is now on the computer. I tried to mount the USB with TWRP and the computer tells me that the drive is "unformatted" and asks to "format?" So far I've cancelled out of that.
Is this device borked beyond repair?
Click to expand...
Click to collapse
So you can actually reboot in recovery ? reformat your sd card (fat32). Try to flash the boot.img of the rom you're on, reflash the romzip and see where that takes you. Note: there seems to be some issue with htc sync while you flash so make sure to disable htc sync.
Hi,
Im trying to root my HTC ONE S. I followed all the steps that suggested in the forums, but when I reboot the phone in the final step, it got stuck in the 'HTC quietly brilliant' screen. I left it there for 20 min or so, it didn't change. I am able to go to the recovery mode but I don't know what to do. I did a factory reset attempting to go back to the original software but it didn't work either. Any ideas what can I do? Im in real trouble if Im not able to use my phone anymore.
Thanks in advance,
Angel
100315595 said:
Hi,
Im trying to root my HTC ONE S. I followed all the steps that suggested in the forums, but when I reboot the phone in the final step, it got stuck in the 'HTC quietly brilliant' screen. I left it there for 20 min or so, it didn't change. I am able to go to the recovery mode but I don't know what to do. I did a factory reset attempting to go back to the original software but it didn't work either. Any ideas what can I do? Im in real trouble if Im not able to use my phone anymore.
Thanks in advance,
Angel
Click to expand...
Click to collapse
Well if you are installing a custom ROM then there is no need to root before hand, you just need a custom recovery installed. The custom ROM will have root access enabled.
If you are asking how to just be rooted on a stock rom, then I would just google how to do it like you would. But I assume you install custom recovery, download a supersu.zip and install via recovery.
tivofool said:
Well if you are installing a custom ROM then there is no need to root before hand, you just need a custom recovery installed. The custom ROM will have root access enabled.
If you are asking how to just be rooted on a stock rom, then I would just google how to do it like you would. But I assume you install custom recovery, download a supersu.zip and install via recovery.
Click to expand...
Click to collapse
Hi, thank you for the reply
Well, I have no access to the sd card, it says it's not mounted. I can't copy any files to the phone, therefore I can't reinstall it from the phone. Sorry for my ignorance, but I don't know what to do next.
Thanks,
Angel
100315595 said:
Hi, thank you for the reply
Well, I have no access to the sd card, it says it's not mounted. I can't copy any files to the phone, therefore I can't reinstall it from the phone. Sorry for my ignorance, but I don't know what to do next.
Thanks,
Angel
Click to expand...
Click to collapse
seems to be a common that the sdcard can become corrupted.
If that is the case, having the stock recovery on and then booting the phone into bootloader and selecting "clear storage" fixes the issue.
Then you need to flash custom recovery again, and mount usb storage.
For the S4 Ville version of this phone and not the S3 VilleC2
stock recovery
https://dl.dropboxusercontent.com/u/84212943/ville_recovery_signed.img
tivofool said:
seems to be a common that the sdcard can become corrupted.
If that is the case, having the stock recovery on and then booting the phone into bootloader and selecting "clear storage" fixes the issue.
Then you need to flash custom recovery again, and mount usb storage.
For the S4 Ville version of this phone and not the S3 VilleC2
stock recovery
Hi,
I tried to do what you told me, but now I can´t even go into the recovery mode. I can only access the bootloader; anytime I select recovery mode it shows this (image below), after a few minutes it reboots and stays with the white screen ´HTE quietly brilliant´. I can´t copy any files either because the computer doesn´t read the sd card. Any ideas?
Thank you for your time.
Angel
Click to expand...
Click to collapse
100315595 said:
tivofool said:
seems to be a common that the sdcard can become corrupted.
If that is the case, having the stock recovery on and then booting the phone into bootloader and selecting "clear storage" fixes the issue.
Then you need to flash custom recovery again, and mount usb storage.
For the S4 Ville version of this phone and not the S3 VilleC2
stock recovery
Hi,
I tried to do what you told me, but now I can´t even go into the recovery mode. I can only access the bootloader; anytime I select recovery mode it shows this (image below), after a few minutes it reboots and stays with the white screen ´HTE quietly brilliant´. I can´t copy any files either because the computer doesn´t read the sd card. Any ideas?
Thank you for your time.
Angel
Click to expand...
Click to collapse
That is good, that is the stock recovery, basically saying you don't have access to it.
But you don't need to go into recovery, it is there just to fix the issue when you enter the bootloader and pick "clear storage"
So get back to the bootloader and clear storage. Then you will need to flash the recovery of your choice, CWM or TWRP. You should now be able to access usb storage. (unless you are using the special TWRP in the Maximus thread meant for hboot 2.16, then it just doesn't work)
Click to expand...
Click to collapse
Yes, it worked. Thank you.
But, which ROM should I install now? I tried with the SU, but the screen was stuck again. Do I need the phone in S-off mode? how do I do that? I saw that many ROM's need this.
Thank you again for your help, very appreciated
Angel
100315595 said:
Yes, it worked. Thank you.
But, which ROM should I install now? I tried with the SU, but the screen was stuck again. Do I need the phone in S-off mode? how do I do that? I saw that many ROM's need this.
Thank you again for your help, very appreciated
Angel
Click to expand...
Click to collapse
You are welcome.
You only need S-Off if the rom says 2.16 HBoot required.
So there are a lot of different ones to try. As long as your Hboot is 2.15, if not then you need to upgrade your firmware to that. You see your HBoot in the bootloader screen.
So ya, most of the roms are ok with S-on, you just have to remember to:
fastboot flash boot boot.img
So on your pc download the rom, unzip it you will see the boot.img move that to fastboot folder and fastboot flash it.
Then you can move the ROM.zip to your phone and install via recovery.
Don't forget to wipe caches before rebooting. (when installing, if that particular rom opens up Aroma installer and one of the options is to wipe, do that but don't wipe again when back to recovery)
The sense based roms are generally more stable and like stock.
The CyanogenMod may have a few little bugs.
Just browse around and see which one you like.
It all worked out pretty well.
I'm trying with the MagioRom, seems to be very stable!
Thank you for your help, you literally saved my HTC!
:good:
I have a one sv which:
is k2 ul
normally boots only to HTC screen (no quietly brilliant) and stays there till the end of times
shows tampered locked, which i now changed unlocked status (htcdev)
s-on
has twrp recovery on, but swipes fail mostly
flashing roms in twrp recovery show success but result is still HTC logo without being quietly brilliant
can not be ruu-ed beucause the ruus i find are i think older than required
hboot 2.21, radio 1.18 version
s-off fails because tho fastboot recognizes phone, adb doesnt in fastboot mode and in bootloader pc thinks it is not attached (tried xp, 7, 8.1 and many different drivers)
i am not sure if usb debugging was on before the phone crashed
so i can't put an older ruu because of s-on, i can't get s-off because rumrunner and moonshine can't work without adb, and basically that is it.
does anyone PLEASE have any idea what to do?
and yes, the warranty is over and the phone has gone to the warranty twice with bootloop before.
After flashing a rom, did you also flash the boot.img of the rom with fastboot cmd?
Thats necessary, because you are S-on.
And what TWRP is installed?
old.splatterhand said:
After flashing a rom, did you also flash the boot.img of the rom with fastboot cmd?
Thats necessary, because you are S-on.
And what TWRP is installed?
Click to expand...
Click to collapse
yes i did.
twrp 2.6.3.2
now i have made such progress that twrp tells me it cannot mount int sd and when booting, phone stays on the htc logo for some seconds and then switches off. i believe i have actually made it worse (didnt think that could happen).
EDIT: so i formatted the storage like this http://forum.xda-developers.com/showthread.php?t=2576897 and it BOOTED
EDIT2: the phone now kind of works IF it boots. half of booting times it just switches off, the other half it switches off and then reboots and works. i think something is still kind of not good but i dont have the b***s atm to poke it more.
thank you all for your potential help.
What rom did you use?
Please also perform a full wipe (without internal/external sd) in recovery under Wipe -> Advanced
old.splatterhand said:
What rom did you use?
Please also perform a full wipe (without internal/external sd) in recovery under Wipe -> Advanced
Click to expand...
Click to collapse
it was this one http://forum.xda-developers.com/showthread.php?t=2512742 which is, as i understand, your work, thank you very much, donations will happen when im a tincy bit richer
and i will wipe some time later when im at home and courageous enough.
You can also try to restore this TWRP backup.
great news! today the phone restarted itself and froze on the logo. i tried to start twrp but it froze on that logo too. tried to do a factory reset, which removed the "tampered" sign until next reboot but that was about it.
now i can't reflash twrp or anything at all, with the error remote: image update error. oh please save me again.
Does not sound good.
You can boot into bootloader? Is it locked or unlocked? Did you reflash the recovery to check if you can boot into it?
looks bad indeed.
i can boot into bootloader, which is unlocked. and please specify what do you mean by reflashing the recovery (pardon my stupid brain)
When in bootloader, connect your phone to fastboot and try to flash recovery again.
If you can't get into recovery, i don't know, if there is much i can do for you
fastboot basically tells me to go f* myself with the error "remote: image update error" what ever I try to flash. right now Im trying to find a way to reflash twrp from ext sd. not doing so great
Well, about your country flag i suggest you speak (or you can at least read) russian language.
Go to 4pda.ru and look for the posts of "MikG". He has made zip files, similar to RUU. They are flashed from bootloader/Ruu mode. Maybe they can bring your phone back to life.
I can't tell you how to use this files, because i don't speak russian.
I'll try, thanks.
edit: and it just refuses to cooperate. it kind of does something in bootloader, but still doesnt boot past htc logo or if i try recovery, it stays on teamwin logo. i dont know if im doing something wrong or what... maybe i'll wait for the 4.2.2 hboot 2.21 radio 1.18 ruu then because i really dont know what else i could do.
Hello, i recently installed the new official lollipop 5.0 android, however it was working like crap so i decided to change with custom firmware.
Heres what i did.
Unlock bootloader
install custom recovery
root with super SU
install custom rom.
It worked, and android started up, however, i cant connect to cellular network anymore, i waited like 10 minute to detect it but it wont, then i tried a different rom, didnt help. Did i bricked my phone? Is there anything to do?
Im with Virgin canada
Thanks
Can you access the bootloader? If yes, then you did not brick it. You probably didn't completely wipe the stock ROM before you flashed the custom one. Also, not a good idea to flash SuperSU before flashing your ROM.
Everything is working has usual, except i cant connect to LTE anymore. I flashed TWRP instead of Clockwork recovery, ill try again with this one...
From where you are now with TWRP installed:
1. In TWRP, go to "Wipe" then go into the advanced wipe options and wipe every partition except the internal storage.
2. Flash ROM.
3. Flash Gapps if needed.
Google "APN"
theesotericone said:
Google "APN"
Click to expand...
Click to collapse
From what ive seen, i have to set it up myself?
Also i currently has no ROM installed, and none in my SD card, i tried sideload but it failed, is there a way to transfert the ROM to my memory card in TWRP? If i have to click USB-OTG for it, then nothing happen when i do.
insistents said:
From what ive seen, i have to set it up myself?
Also i currently has no ROM installed, and none in my SD card, i tried sideload but it failed, is there a way to transfert the ROM to my memory card in TWRP? If i have to click USB-OTG for it, then nothing happen when i do.
Click to expand...
Click to collapse
Push the ROM zip file to your phone from within TWRP, don't sideload it. You shouldn't even need to do that though. TWRP now supports MTP so your internal storage should appear when you connect the phone to the PC when you're in TWRP.
So you went from having possible APN issues to completely wiping your device? Slow down before you actually do brick it. Read the stickies. All the info you need is already here.
Brushstroke said:
Push the ROM zip file to your phone from within TWRP, don't sideload it. You shouldn't even need to do that though. TWRP now supports MTP so your internal storage should appear when you connect the phone to the PC when you're in TWRP.
Click to expand...
Click to collapse
-snip
Had to turn off MTP
theesotericone said:
So you went from having possible APN issues to completely wiping your device? Slow down before you actually do brick it. Read the stickies. All the info you need is already here.
Click to expand...
Click to collapse
I followed the stickies, im not sure what i could have missed.
insistents said:
I tried "adb push rom.zip /sdcard/"
but it say
error: device not found
Click to expand...
Click to collapse
Nevermind.
insistents said:
Hello, i recently installed the new official lollipop 5.0 android, however it was working like crap so i decided to change with custom firmware.
Heres what i did.
Unlock bootloader
install custom recovery
root with super SU
install custom rom.
It worked, and android started up, however, i cant connect to cellular network anymore, i waited like 10 minute to detect it but it wont, then i tried a different rom, didnt help. Did i bricked my phone? Is there anything to do?
Im with Virgin canada
Thanks
Click to expand...
Click to collapse
Try wiping your cache in TWRP.
Brushstroke said:
My bad. TWRP, as far as I can tell, only allows sideloading as far as ADB commands are concerned. Can you not mount the SD using the Mount option in TWRP?
Click to expand...
Click to collapse
I managed to push files by disabling MTP
However, im still waiting on that colour dot loading screen...
insistents said:
I managed to push files by disabling MTP
However, im still waiting on that colour dot loading screen...
Click to expand...
Click to collapse
Which screen are you referring to?
Brushstroke said:
Which screen are you referring to?
Click to expand...
Click to collapse
Boot screen, where there are flying colour dot.
By the way, i only have managed to enter TWRP recovery once, for all the other time, there only was the Teamwin picture, then it reboot to android each times...
insistents said:
Boot screen, where there are flying colour dot.
By the way, i have to do "fastboot flash recovery recovery.img" each time if i want to acess TWRP
Otherwise it wont work, when i go to recovery mode, i can see the TeamWin picture appear for a few second, then the phone reboot to android.
Click to expand...
Click to collapse
Well, did you flash a ROM or factory image? Earlier you said there was no ROM installed.
And about that TWRP issue...not too sure. That could be the recovery_from_boot.p file restoring the stock recovery. Are you seeing an android with a red exclamation point?
Brushstroke said:
Well, did you flash a ROM or factory image? Earlier you said there was no ROM installed.
And about that TWRP issue...not too sure. That could be the recovery_from_boot.p file restoring the stock recovery. Are you seeing an android with a red exclamation point?
Click to expand...
Click to collapse
There was none earlier untill i managed to push a rom in the memory card, but now the Rom just wont start, its stuck in the boot screen so i will try a different ROM.
Nope no red exclamation point, when i choose recovery mode, the Google boot screen appear, then the Teamwin logo appear for a few second, then screen goes black and then google logo is back, and finnaly android boot up...
Ah well i think i fixed the recovery, i used an older version and now its starting properly.
insistents said:
There was none earlier untill i managed to push a rom in the memory card, but now the Rom just wont start, its stuck in the boot screen so i will try a different ROM.
Nope no red exclamation point, when i choose recovery mode, the Google boot screen appear, then the Teamwin logo appear for a few second, then screen goes black and then google logo is back, and finnaly android boot up...
Click to expand...
Click to collapse
Which ROM is this? And since you've already wiped the SD card once and the ROM won't boot, why not just flash the factory image so you'll have a clean slate to start with?
Factory image = Official firmware?