Hey Guys!
I'm a bit new here, but I have register to become an answer to my question which I haven't found yet.
I've flashed my HD2 with tytung's "NexusHD2-ICS-4.0.3-CM9 V1.0" (with task29, radio reinstalled, hspl reinstalled, maglrd reinstalled & cwm reinstalled).
the problem is: after minutes of bootscreen I have to enter my Pin, I do.
There is given the text "Unlocking SIM" , while "he" do so, de screen turns black and I have to enter my Pin again and again. Sometimes he simply accept and go on, but then many process' crash! Process' like: android.process.acore , google.process.gapps, com.android.phone android keyboard ..
they all crash in a row and latest then I have to enter my Pin again.
Could anybody help me?
did you try to reflash the rom?
go to recovery, wipe data/factory reset & advanced -> wipe dalvik cache
after that, install the rom again.
I also have the issue that my phone stucks at the htc screen...i wait for 20 minutes now but nothing happens...i'll try to flash a bigger partition layout magldr...
Try the SD build
Hi, too bad you are having difficulty.
I am running the SD version of the same OS with do problem.
Two options:
Try the SD build:
http://forum.xda-developers.com/showthread.php?t=1437463
Just remember to rename the Folder to ICS, then tell MAGLDR to boot from SD / ICS
or try going back to a stable ROM, remove all PIN codes, then reinstall CM9
Good Luck
i have already removed all pin codes.
also i tried a full wipe with task29 and used the 250mb system partition because i read something about bad nand blocks.
earlier i tried to boot some sd builds that were made for boot with magldr, but without any success...if i go to the selection of the android sd folder in magldr it just pushes me back to magldr main menu :/
my hd2 is difficult to understand because it doesn't work as others do >.<
RichieGKB said:
did you try to reflash the rom?
go to recovery, wipe data/factory reset & advanced -> wipe dalvik cache
after that, install the rom again.
Click to expand...
Click to collapse
First: thanks, that there are people which consider to be with me with my problem
yea, i've already reflashed the rom (felt like 20 times!) ..
and I've actually tried to install no sd-version, I kept it as a loophole. ^^
Situation now: I've simply ignored the messages that every important process is going to die and just clicked the failures away. after that he wants to reboot, to get access to the mobile network --- I click "Reboot" und have now a Bootloop ...
i also tried another ics rom without cm9 and got the bootloop at the first boot...
I dont understand why no rom is running on my phone...
So guys !
I've done it ;D
Have simply used the sd-version and it works great!
@RichieGKB: If you have any question to the sd-version, message me !
Good post Charles, it helps me.
Seems to helps you too guys. Don't forget to hit thanks button!
i tried the full wipe and also a larger system and cache partition to get the rom working, but it still doesn't on nand.
I'm downloading the sd version at the moment, but this can't be the solution for the future :/
maybe i have to wait for newer versions of this rom
ah I solved the problem.
I didn't change the system partition layout in recoverys .cfg file. I didn't know that i have to do this because i thought it would be enough to install another version of magldr
@weedstar: Thats not the problems solution.. next time try to fix permissions via CWM. Sd version is slow. Nand is better.
Hf
Sent from my NexusHD2
Related
Someone please help me!! Before all i problems my phone kept freezing in boot and i tried everything by cleaning my sd, ad hard reset and changing builds and the same boot freeze kept happening. So after getting tired of that and having to hard reset everyday i eventually flashed TMOUS stock rom then after tried to do the magldr 113 isntall. I got magldr installed on my phone and then i choose the ad recovery. When i do i get this message "no boot source". I tried looking up on these forums and can't find anything to fix my problems. Someone please help me with a step-by-step guide. I don't want to own an hd2 running the crummy wm6.5 :/ I NEED ANDROID
download hd2 toolkit. afterward install magldr update recovery, follow the prompts to install and your done. in a nutshell...you were missing clockwork recovery. let me know if this helps
danielfc741 said:
Someone please help me!! Before all i problems my phone kept freezing in boot and i tried everything by cleaning my sd, ad hard reset and changing builds and the same boot freeze kept happening. So after getting tired of that and having to hard reset everyday i eventually flashed TMOUS stock rom then after tried to do the magldr 113 isntall. I got magldr installed on my phone and then i choose the ad recovery. When i do i get this message "no boot source". I tried looking up on these forums and can't find anything to fix my problems. Someone please help me with a step-by-step guide. I don't want to own an hd2 running the crummy wm6.5 :/ I NEED ANDROID
Click to expand...
Click to collapse
do this...depending on the recommended recovery size (typically 5-150-5 for non sense versions) download a recovery from here ..then restart you phone...go into magldr...go to flasher...once the usb is linked to pc run daf.exe from the recovery (extracted folder)...u will then have recovery installed
gdsbalaji said:
do this...depending on the recommended recovery size (typically 5-150-5 for non sense versions) download a recovery from here ..then restart you phone...go into magldr...go to flasher...once the usb is linked to pc run daf.exe from the recovery (extracted folder)...u will then have recovery installed
Click to expand...
Click to collapse
YOU SIR ARE GREAT!!! thanks so much!!!!! i can now use android! im glad it works.
Welcome...glad it worked
Sent from my HTC HD2 using XDA App
gdsbalaji said:
do this...depending on the recommended recovery size (typically 5-150-5 for non sense versions) download a recovery from here ..then restart you phone...go into magldr...go to flasher...once the usb is linked to pc run daf.exe from the recovery (extracted folder)...u will then have recovery installed
Click to expand...
Click to collapse
Great ! I will try it out as well. I have been getting this error for the last few times. I am not sure why this happened.
I installed a WP7 rom and then went back to android (hopeless battery drain with my SD card ... not sure if I can ever do something about that). I could not get back to AD recovery.
Thanks again !
gprash said:
Great ! I will try it out as well. I have been getting this error for the last few times. I am not sure why this happened.
I installed a WP7 rom and then went back to android (hopeless battery drain with my SD card ... not sure if I can ever do something about that). I could not get back to AD recovery.
Thanks again !
Click to expand...
Click to collapse
If you loaded WP7 it may have locked your SD Card - need to format in a Nokia phone. Or reduced the usable size to 200mb - this can be fixed with a partitioning tool from PC
when go back and forth between WP7 and Android the nand is overwritten ... thats why you loose your AD recovery.
REMEMBER - if you ever try WP7 and come back to Android dont forget youll need to task 29 (to clean out that nasty M$ dirt!), flash magLDR, flash recovery ( i usually stick with a 200 mb partition, as i usually run Hyperdroid, AND that way there are no worries about bad blocks), and then the rom.
although its not NECESSARY its recommended buuuut to avoid weird restarts, FCs, and any other random glitches that may occur down the short road ITS NECESSARY! :-D
good luck
hello everyone! I just installed android on my HTC HD2 successfully but when the phone reboot, shows me the MAGLDR says me that android booting from start and I have to setup android everytime I reboot the phone from the start. someone help me passing this step. thankyou in advance
hi
i installed many rom on hd2 via clk cwm .zip from sd card many rom stuck on start up but some starts but after restarting or powering off the the same problem with all roms plz help to boost ur thanks meter
Make sure you perform "wipe data factory reset" in cwm, to ensure the files on the ext and android folder on fat32 are cleared before flashing the rom.
If possible try a different SD card and sim, they can both cause issues occasionally.
Any stability issues on winmo?
Just give us more info about that ..
Are you sure you are using correct system partition size?
Any SD-ext? Sense (big) roms?
Did you try complete reflash? (-> winmo -> hspl -> radio -> clk+cwm -> android)
You (We) can check your logcat, there should be answer for this issue.
i dont know about the system partition i think this is the problem some roms need
160/5 mb system partition how to do this partition
I had the same issue and I redownloaded and reinstalled CWR from this post:
http://forum.xda-developers.com/showthread.php?t=1044830
I used the 400mb file from the post.
Cheers
tauqeer512 said:
i dont know about the system partition i think this is the problem some roms need
160/5 mb system partition how to do this partition
Click to expand...
Click to collapse
any rom you flash will tell you in post 1 what size partition to use.
asbestos said:
I had the same issue and I redownloaded and reinstalled CWR from this post:
http://forum.xda-developers.com/showthread.php?t=1044830
I used the 400mb file from the post.
Cheers
Click to expand...
Click to collapse
thats a fine fix, however if you flash a smaller rom to that, you will waste the extra space. so flash a 250 meg rom to a 400 meg partition, you will lose 150 meg, it wont be used for apps or data, the system will just ignore it.
Every time u flash do TASK29,RADIO,MAGLDR,CWR ,FORMAT SD,PARTITION SD then put rom on it then flash it. Everytime i do not follow that procedure i stuck on boot
Always Task 29.
Cjovecje! said:
Every time u flash do TASK29,RADIO,MAGLDR,CWR ,FORMAT SD,PARTITION SD then put rom on it then flash it. Everytime i do not follow that procedure i stuck on boot
Click to expand...
Click to collapse
Hello guys,
I am experiencing the same problem with my HD2.
I have Tasked29, flashe MGLDR, CWR, formatted and partitioned SD, then placed ROM file and flashed. I reboot and the phone gets stuck on the HTC screen. The flashing of the ROM takes very little time. Before I had this problem, flashing a ROM would take longer than what it does now. It completes in about 10 seconds or less!
I can't figure out what's wrong. I had to re-install an old ENRGY Windows ROM; better than nothing! This ROM is working fine, even without the SD card.
I had been flashing CWR 4.0. I will flash 3.0.2.5 and see what happens.
Any one has any ideas please?
cubexe said:
Just give us more info about that ..
Are you sure you are using correct system partition size?
Any SD-ext? Sense (big) roms?
Did you try complete reflash? (-> winmo -> hspl -> radio -> clk+cwm -> android)
You (We) can check your logcat, there should be answer for this issue.
Click to expand...
Click to collapse
thanks for reply how can i make partition i have problem with my phone usb port board damage and could not connect to pc. help plz
tauqeer512 said:
thanks for reply how can i make partition i have problem with my phone usb port board damage and could not connect to pc. help plz
Click to expand...
Click to collapse
Follow this tutorial by kylew1212 to install cLK 1.5 . (don't forget to thank him)
After it installs, boot while holding the back button > Settings > Repartition NAND > *After you finish selecting your sizes* choose "COMMIT" .
Phone will reboot, then go to "Recovery" and flash your rom from there.
Hi All,
I am new here and this is my first post. But i have been reading this forum for quite sometime and know that u guys are now my final stone. I am a proud owner of a Motorola Defy. And I am having this strange behavior, which is effectively rendered the phone almost useless. The phone is acting like its got a restore point in itself, and every time i restart.. it gets back to that point in time.
This includes app installs, uninstalls, stuff placed in system through adb push, theme, everything in the OS. I tried installing a different ROm through clockworkmod, but its not taking effect. Its saying install success but as soon as it restarts, its going back to the old ROM. (takes time to load, so i guess it reinstall back/restored the old version)
Details of device : I am from India and the phone was manufactured in India in around April/May 2011. Its a red lens Defy and and came with Eclair. I updated it officially to the first Froyo release for SEA region. After that i rooted the phone with superone click, and installed WIUI rom. I have been updating the ROM with newer versions around each month. The last one was 1.11.18 though as i waiting for a good ICS version to flash.
The problem occurred after i started installing some gold apps from getJar. It restated in between and install... and that point is kind of acting like a restore point even now.
Things I did: Tried installing different rom by CWM method. Reinstalling second init and CM, both old and new version. Tried restoring nandroid backup of my official ROM. Tried fixed and full sbf flash through rsdlite 4.9.5.2 and now 5.6. First 3 things reset as soon as i restart. For RSDLite, it gives checksum error for each and every ROM i tried. I tried all SEA releases, JORDN_U3_97.21.51, Defy Plus Rom 2.3.6, 2.21 first eclair rom, everything gives the same error. From the RSDLite logs, i could see that there is something wrong as.. say the last successful CG was 33, and the error came for 34, the log says its expecting the checksum on the sbf to be equal to that of CG 33. Its taking the last successful checksum validation and expecting that for all the CGs henceforth. its not showing what the device actually has.
I atlast could somehow, but trial and error, removed all the CGs which were throwing error, and recompiled the sbf to make it pass the RSDLite flash. The CGs present in the ROM (JRDNEM_U3_3.4.3-36-1.7) were 32, 34, 42, 53, 61, 64, 65. And as soon as it booted, it restored back to the checkpoint. Even after i formatted by card and put it in, the app shortcuts remained on the home screen, but as the apps on the card were gone, they are just junk and doesnt open anything.
Thanks in advance. Please let me know what you need from me to help me resolve this issue.
Any help... Anyone?
Can someone please suggest something?
This is what i got from some people. I am not sure how far this is possible, but somehow the theme i installed just before this all happened, from MIUI market.. somehow managed to change something inside phone's kernel, past the locked bootloader? I am totally a noob in this and just a wild imagination?
Or may be some sort of cache wipe is happening everytime the phone boots up, So even when i install the ROM, when it boots up, it gets back the old ROM.. like what would probably happen if i do a factory reset soon after i instal a rom before the restart..?
I would really appreciate it if anyone could help me out with this...
Checksum errors were for me also.
I tried my office computer for flashing and instantly flash was done. The checksum error occurred 7 times on my good computer before that.
Reflashing froyo must take care of all errors happening
Thanks Kapil fr the response. Are you from india? Which sbf did u flash? And waht all did u install in the office pc? I have a pc of my friend where i can try to reflash if you tell me the exact steps that u took in the fresh pc.
Also, can anybody tell me how to use adb commands in CWM mode? Its recognizing my phone in normal mode but as soon as it boots in Moto recovery of CWM, its not recognizing anymore. Want to use adb format commands from recovery.
Hi I was able to use adb in CWM, but format commands were not working. How can i format the system partition? please help me with this.
Is there anyone here who know how to restore a nandroid backup manually using adb commands for MB525???!!!!!
Sounds weird and impossible. Try this. Wipe everything though cwm and flash new rom. Try ms2ginger.
Thanks darshanonline for the suggestion. I tried to wipe everything.. factory reset+cache+dalvik cache wipe. And then tried to install cyanogenmod 7.1 as well as 3 different wiui builds. Everytime it shows that the install was successful, ut as soon as i restart, it would go back to the old ROM.
Is there any checkpoint system in android, seeing the init.rc, i can see comments on something about saving a checkpoint. Is there any particular condition under which this checkpoint may be getting used on very restart?
Also.. is there any way for RSDLite to skip the chksum validations and get the install anyways?.. Some sort of a hack into it?
Ok.. Found something else thats happening. I dont need to shutdown for the system to revert back. Say i install a few things new after a reboot.. After some time.. 1 day at max, i am not able to open them, and neither am i able to open manage applications or market. Everything force closes. I have Ti Backup installed, and i opened it, and i didnt find the new apps to back up. I connected the device and checked through adb, and they were not present in the app folder. They just vanished... So basically after a certain point of tiime, the new stuff just gets deleted on its own.
Guys i know i may sound dumb and stupid with my questions, but i really couldnt find any solution on the net for this. Please tell me waht i should do, and i'll do it. But tell me something. Dont ignore please!
and you did wipe data from within stock recovery (vol down+power etc.), i presume..
Sent from my MB526 using Tapatalk
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Soumik84 said:
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Click to expand...
Click to collapse
DL WIUI 1.12.16 ICS > copy to SD card > Boot in CWM > select zip to install > Install WIUI 1.12.16
Hopefully your problem should be solved.
I found 1.12.16 ICS with lesser FC than the 2.21
labsin said:
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Click to expand...
Click to collapse
Thanks for the link. Now i know that i am not the only one having this issue. But even there its not resolved yet.
@ headers.chennai - Thanks. I will try that ROM, along with Pikachu ROM with Aroma installer, might be a different installer can try fix it?!
BTW.. does anyone have the TI OMAP board utility? Any chance that it can be available outsite here?
I tried the arora installer and it supposedly formatted the system partition and remade it.. but as soon as it finishes and i restart.. I get back the same ROM.
Is it some way that the files are not getting deleted, like some hardware lock or fault?
Soumik84 said:
I tried the arora installer and it supposedly formatted the system partition and remade it...
Click to expand...
Click to collapse
Hi, bro! What is "arora"? I should try it asap, and all other chance.
My trouble here, same as your.
Hey man.. looks like we are having same problem...
Sorry abt the typo... its Aroma Installer. Its with the Pikachu ROM in this link :
http://forum.xda-developers.com/showthread.php?t=1498843
Its a new installer that launches from cwm when u try and install this ROM. u got some options to select and on selecting the complete install option,, the log shows that it formats the system partition and then creates it. I saved the log file, but for some reason the file shows up blank now. Might be problem with the launcher.. or my phone.. dont know.
Soumik84 said:
Its a new installer that launches from cwm...
Click to expand...
Click to collapse
Not for me, my checkpoint without cwm
Hi everybody.
Has anybody esle problem with stuck on boot logo MIUI after flashing MIUI ICS 2.6.8 Ported by smokin901 [tytung r3 HWA]?
I have been used the MIUI 4 by smokin for 2 months without any problems. Every week I was able to flash it without stuck on boot logo.
I was trying to make a clean install (as always):
1. Wipe (Task 29)
2. Instal clk 1.5
3. Check partition size (220/5)
4. Flash MIUI 2.6.8
5. without reboot install Bootloopfix 2.6.8
6. clear dalvik cache (as it appears after installing bootloopfix)
6. Reboot - and then my phone get stuck on boot logo MIUI (I left the phone like that for 30 minutes without no succes).
Did I miss something important?
I also tried to flash radio version again: Leo_RADIO_2.15.50.14, but it did not help. When I got back to 2.6.1-2 MIUI - everything is just fine.
Thanks for any advice what else can I try.
peto.zalesak said:
Hi everybody.
Has anybody esle problem with stuck on boot logo MIUI after flashing MIUI ICS 2.6.8 Ported by smokin901 [tytung r3 HWA]?
I have been used the MIUI 4 by smokin for 2 months without any problems. Every week I was able to flash it without stuck on boot logo.
I was trying to make a clean install (as always):
1. Wipe (Task 29)
2. Instal clk 1.5
3. Check partition size (220/5)
4. Flash MIUI 2.6.8
5. without reboot install Bootloopfix 2.6.8
6. clear dalvik cache (as it appears after installing bootloopfix)
6. Reboot - and then my phone get stuck on boot logo MIUI (I left the phone like that for 30 minutes without no succes).
Did I miss something important?
I also tried to flash radio version again: Leo_RADIO_2.15.50.14, but it did not help. When I got back to 2.6.1-2 MIUI - everything is just fine.
Thanks for any advice what else can I try.
Click to expand...
Click to collapse
Due to Bad NAND blocks which your phone might have, you have less than 220mb when you partition your internal memory. So when partitioning, make a partition of say maybe 230 or 235mb so as to account for the bad NAND blocks
Hope it helps
OK - thank you very much for your advice . I will try it after I get back from work.
Another question is - is there any solution or method, how to check, if my phone really has bad NAND blocks or not? Or maybe - what is causing this bad NAND blocks?
Anyway - I will try it. Thank you very much for the tip.
i prefer this way. you can try if you want.
sequence;
first check your device if it is 2.08.HSPL, and format your sdcard ext3 or ext4 and 1gb. insert it to your device.
1. task29
2. radio rom 2.15.50.14
3. magldr 1.13
4. recovery 5.0.2.6 or clk
5. clear cache and dalvik cache.
Radio ROM 2.15.50.14;
Radio ROM 2.15.50.14
HD2 Toolkit 4.2.0.1; ( contains task 29, magldr and recovery and also HSPL)
HD2 Toolkit 4.2.0.1
peto.zalesak said:
OK - thank you very much for your advice . I will try it after I get back from work.
Another question is - is there any solution or method, how to check, if my phone really has bad NAND blocks or not? Or maybe - what is causing this bad NAND blocks?
Anyway - I will try it. Thank you very much for the tip.
Click to expand...
Click to collapse
You can search the forum for bad NAND blocks. I dont have alot of time currently so i didnt post the link. But will do later
powerofthink said:
i prefer this way. you can try if you want.
sequence;
first check your device if it is 2.08.HSPL, and format your sdcard ext3 or ext4 and 1gb. insert it to your device.
1. task29
2. radio rom 2.15.50.14
3. magldr 1.13
4. recovery 5.0.2.6 or clk
5. clear cache and dalvik cache.
this is the HD2 Toolkit ; http://www.mediafire.com/?2qz0xa7xfxney47
this is the radio 2.15.50.14 ; http://www.mediafire.com/?1th8o158r2t6dba
Click to expand...
Click to collapse
And this will help HOW?
The person has already tried the clean installation. How will doing it again help?
Thanks for any advice, I found some threads,
e.g. http://forum.xda-developers.com/showthread.php?t=1189544.
I am going to study, what should I do to check nand blocks on my hd2.
[Solved]
Thanks everybody for tips, I probably (as a lot of people do) have some bad blocks.
Anyway, I just cut out some application from ROM before flashing and flashed the rom even with lower (200 mb) partition.
But your ideas led me to stuff like bad blocks etc, so now I am able to understand things better and know that flashing too much can cause trouble....
Sent from my HTC HD2 using XDA
Hello everybody
Just to describe the problem I quote what I've written here:
http://forum.xda-developers.com/showthread.php?p=32054164&posted=1#post32054164
Hello everybody
I've got a little problem... after a system crash (don't ask me how that happened) I had to re-flash my ROM. Now, after the reboot the "H" was flashing on my screen and turning around 'n around 'n around... after 30 minutes I plugged out the battery and re-plugged it in. Since then I’m not able to boot into Android, I only get the “Android” Text and Logo on my screen but the “H” doesn’t appear anymore.
I tried to re-flash the Rom and also wipe my device (task29), re-flash clk (I got now the 5.0.2 ClK Recovery) and HBoot. But I’m not able to boot the device. I also tried to flash other CM7 Roms (Partition 160 MB, Cache 5MB) but it doesn’t work for me
Anyone got an idea?
**********************************
Click to expand...
Click to collapse
Originally Posted by plasmastrike View Post
I had this exact problem a while ago, Where every ROM I flashed was corrupted. My issue was caused by bad NAND blocks. the H boot screen in Hyperdroid ROM is the boot animation. The android test boot screen is the default boot screen in android. The reason you got that is probably because your bootanimation.zip got corrupted somehow, so it loaded the default one in android. bad NAND blocks can corrupt everything and it starts getting worse as you flash new ROM's and use because of its hardware limitations.
There are two ways of fixing this problem. One way requires you to use Mutty and was technical and mayby had a chance destroy your NAND, I don't remember because it was a while ago I was researching this.
The other solution which is what I recommend and did because it is a lot simpler and easier is to work around your corrupted block. You can do this a couple of ways:
Firstly, a way is to use CLK 1.5 to move a partition over the problem. For instance if you had a bad block around 25 put the first partition recovery partition to 30 MB. Then you can enjoy flashing ROM's again without the NAND problem. I have this solution working now.
Secondly, another simpler way is to use an Android SD ROM to bypass the corrupted block on you internal NAND now and forward into the future.
For more information about bad NAND blocks and to figure out if you have them and where they are go to:
http://forum.xda-developers.com/show....php?t=1189544 (Application)
http://en.wikipedia.org/wiki/Flash_memory#NAND_flash (Theory)
Click to expand...
Click to collapse
We'll thank you for your fast answer. I tried various sizes of the partitions but none worked for me. I now got a error msg in H Boot "A unrecoverable error occurred" and the phone shots down. Also I don't get any of the "bad block" errors in my recovery log when erazing and re-installing a ROM.
I hope you can help me out
Can I use a SD Rom and boot it via H Boot?
Edit 2: So now after flashing a ROM and rebooting with Clockwork Mod it starts himself, than shuts himself down after a few seconds with the HTC Logo, than boots into H Loader... and always the same error message: "A unrecoverable error occurred, rebooting to Bootloader"
Click to expand...
Click to collapse
I now reinstalled everything with the American Android starter Kit, installed CLK 1.4.0.1 & RUU 190 _ 5 image (190 system, 5 cache) and tried to flash a ROM.
ClK Fastboot stops saying:
fastboot_init()
udc_start()
-- suspend --
What can I do now?
Yes I already tried to wipe dalvik cache, format boot.... I think the problem must be somewhere else...
Please help me!!
Well it seems that I fixed the problem... I found a old Backup from a new flashed ROM in Clockwork Recovery. I flashed that and my phone did boot again.
Cannot understand what happend. Is it possible that moving the ROM files to flash on the sd card can corrupt them?
Blacklight-IT said:
Well it seems that I fixed the problem... I found a old Backup from a new flashed ROM in Clockwork Recovery. I flashed that and my phone did boot again.
Cannot understand what happend. Is it possible that moving the ROM files to flash on the sd card can corrupt them?
Click to expand...
Click to collapse
got the same problem only thing that helped me was to remove all and reinstall it again from the beginning with task29