Hi! I have a bricked ZTE Libra (Sapo A5 in Portugal) and no mather how much I search for solutions I only seem to make things worse, so I was hoping someone here could help me.
Things started to go wrong after flashing a CyanogenMod rom. Everything worked except two things: I couldn't use anything that required my SIM card (so no phone or messaging) and I could not access the recovery screen (clockworkmod).
Without the recovery screen, I turned to ROM Manager but since it uses clockworkmod to do its work it didn't help.
Then I started trying other ways to recover my phone, until I tried ADB which allowed me a shell in my android. But then I broke it all by doing "wipe system" which cleaned my system of everything that was still working and left me with an expensive brick.
Now all I can do is boot until I see the green droid. If I don't press the volume buttons it goes into "device" mode and I can see it listed under "adb devices" but have no idea what to do with it.
If I press the volume button down to go into recovery mode it keeps flashing but never really goes anywhere.
If I press it up to go into the bootloader it stays the same and the only thing I can use to tell me something is different than the normal mode is that lsusb reports the vendor as "Google Inc." instead of what it reports in normal mode: "ONDA Communication S.p.A.".
With this I'm not even sure if I can get to the bootloader or not, but even if that is the bootloader, I have no idea what to do with it that might help me recover my phone.
By the way, I'm trying all this on Linux, although I could try solutions in Windows if required.
Can anyone tell me what can I do in this situation?
Ok, maybe my first post wasn't that easy to answer, so I'll make a simpler question to see if someone can help me.
What can be done at my android's bootloader? What is it for and what tools do I need to use to do it?
You could try installing ClockworkMod recovery using wbaw's guide here http://forum.xda-developers.com/showthread.php?t=1319257 Once that's installed you should be able to flash a new rom with it.
In bootloader mode you can flash a new kernel or recovery image using fastboot.
If you follow that guide that I wrote & Amphoras linked to then you should be able to get a working clockworkmod installed and then you can use that to flash a working rom, or restore a backup.
Thank you both, I'll try what you said as soon as I can and then I'll let you know if it worked!
Ladies and gentleman, today a miracle happened, my ZTE came back from the dead!
Apparently the problem was that I installed some GEN2 applications on my GEN1 model.
I found this while reading the tutorial you suggested, after which I upgraded my ZTE to GEN2 which allowed me to slowly recover everything else.
So, I have to say, thank you very much, and I hope I won't need your help again anytime soon! xD
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Few questions first... (I am an Android n00b, but have had issues and flashed custom ROMs about 9 times now.)
Did you make sure to see if the device was properly detected in your OS of choice beforehand? Installed all the software to do so?
Did you install either CWM or TWRP to the device?
Make a recovery in case of issue?
I followed the topic (in this very forum) about flashing. I had some issues being new and all, but got it right... BEFORE I did an actual flash.
[GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
I am using the latest TWRP instead of the guides CWM advice. Due to CWM failing to create a backup for me. I felt not having a backup plan, was something similar to going to a redlight district without a rubber. Which means... What if something goes wrong, how will I fix it?
Does the device detect? Can you move files to the device from your computer?
techknewz1 said:
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Click to expand...
Click to collapse
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Xynergy said:
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Click to expand...
Click to collapse
So here is what happened. Basically i tried flashing files and put it for the wrong tablet. Now i can only get into apx mode and fastboot doesnt recognize it and neither does adb recognize it.
Hello,
I had installed the Franco Kernel on my N4 some months back. I recently got the 5.0 Lollipop OTA update but i could not install it. I read somewhere that i needed to install the stock kernel to get Lollipop installed. So i got the factory image of 5.0 for N4 from google and manually tried to flash with some Kernel flasher app i dont recall the name. THAT WAS THE WORST DECISION I EVER TOOK.
Now my phone is stuck in fastboot mode. I can go to recovery and all. Whwn i try to start up my phone i can only see a black screen.. i downloaded adb but the problem is I HAD NOT TURNED ON USB DEBUGGING. I searched the net for a week,asked my friends who all said that i should throw away my old( i dont consider it old) phone and get a new one. I have come here with a lot of hope. I bought the N4 so as to use it for atleast another year .
Adb doesnt recognize my phone. Pc says "Android Device". Please help me. Im saving for getting my sister a laptop and i just cant afford another decent reliable phone.
You do not need USB debugging for fastboot mode. when cionnected is should say android device and some serial number.
USB debug mode is when the android OS is running not fastboot mode
if it does not when connected at the prompt type fastboot devices
follow the install instructions here and it should get you device back. (in the commands remember to replace the file names with the lollipop names)
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
I have brought back at least 10 devices from my own doing and from people that screw up their phone and not know what they are doing.
Good luck
Ok i will follow it. I currently have the 4.2.2 image file. Yes in fastboot mode PC recognizes it as Android Device. Lets hope i can do it I dont need USB debugging right ?:silly:
I dont know how i should thank you and this forum. I love you guys, you helped me when i had lost all hopes of getting my phone back i love you guys <333333333333333333333333333333333333333333333333333333333333333333
Glad it worked. Just spread the love on the forums.
I learned by reading here and glad to help others.
DO NOT FLASH HYDROGEN ROMS ON HELIUM, OR YOU GONNA HAVE A HARDBRICK.
IN CASE YOU HAVE ONE, HERE IS THE SOLUTION.
This was tested with Xiaomi Mi Max 128GB helium and localized rom from xiaomi eu.
I am not responsible for bricked devices or anything else. So at your own risk:
1. Install official MiPhone drivers
2. Download and install MiFash beta.
3. Download and unpack TWRP for miflash: 32gb or 64-128gb thanks @Abdess76.
4. Download ROM for your device, I recommend to try this one. You can install RR/CM Rom as well.
5. Run MiFlash with admin rights.
6. Turn off the phone, plug the cable to PC and halfway to the phone.
7. At the same time press Volume + and Volume - and plug in the cable.
8. Refresh MiFlash phone should show up. (If it didn't then make sure you did it right and u got drivers)
9. Navigate to your unpacked TWRP and flash it.
10. Now, boot ur phone with volume up. It's a bit slow. If it's stuck on miui logo, just release button and wait.
From here start to pay more attention:
11. TWRP can ask for password, press cancel and allow modifications by moving slider.
If you just need ROOT and your current rom, skip to the step 16. Also there is a recovery from boot in system folder. If you won't remove it, recovery may be replaced with stock one after reboot. Keep it that way if you want OTAs.
12. Format data.
13. Enable MTP and put modified zip in your phone.
14. Go to mounts and unmount system **
15. Flash your rom.
16. Flash latest supersu.
17. Reboot the phone.
In case u got NO OS message, then it means that u probably ignored step 15.
Also first boot may take like 15-20 minutes, since eu rom is deodexed.
Just to be sure, after installation mount system partition and navigate to the /system folder using TWRP's file manager and make sure it's not empty.
* In my case system didn't install because script could mount system partition since it was already mounted.
P.S. In order to update, you need to install OTA for offical rom via TWRP. Then without rebooting flash SuperSU, and finally using TWRP's file manager navigate to system folder and delete file named recovery from boot. Doing so will keep root and recovery.
Thank you so much for the guide! I will try it tonite
Waiting for boot loader is just too long..
WOW!!!! Just, wow..... I can not believe it but it worked like a charm. It took me forever to figure out my issue with the drivers, but after solving that I followed you step-by-step. And, lo and behold, it WORKED! Note for other users, Twrp took about a minute or two to finally boot up and it took me personally about 15-20 minutes before MIUI 8 finally booted. Just wait it out and you should have the amazing results that Doom Slayer has so graciously provided you
THANK YOU!!!!
I just done following your guide and it works!!
For rooting, I tried 2 times before it works. I believe you missed out a step to mount back system before flashing supersu.
So in the future, how do we dirty flash? Start from step 13?
How about clean flash? Start from step 12?
Thank you once again for this great guide!!
You saved me a lot of time waiting for Bootloader approval.
flywithme said:
I just done following your guide and it works!!
For rooting, I tried 2 times before it works. I believe you missed out a step to mount back system before flashing supersu.
So in the future, how do we dirty flash? Start from step 13?
How about clean flash? Start from step 12?
Thank you once again for this great guide!!
You saved me a lot of time waiting for Bootloader approval.
Click to expand...
Click to collapse
Yeah, dirty flash is you keep your data and format system and caches .
Clean flash is u format data as well.
The thing is that u have root, and ur phone is also secured. It's linked to ur Mi account, while it's locked. It's better to keep that way
Theoretically If you will ignore steps from 12 to 16. (Maybe u can ignore data formatting too)
Then you can get a ROOT and TWRP on your current rom.
And also theoretically while on miui 8 rom ,u can try to unlock bootloader without waiting.
Try this manual.
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
agreusar said:
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
Click to expand...
Click to collapse
Open it up and remove battery for a few minutes, then try again from step 6...
agreusar said:
I have followed these steps and bricked my phone, spent the last 24h trying to recover it no luck.
I got an error while in the process of flashing the rom at step 16, then tried again and phone went black, stopped responding.
It's not detected using adb or fast boot, it appears in device manager as "Qualcomm HS-USB QDLoader 9008" or "Qualcomm HS-USB Diagnostics 900E", I have tried to flash again TWRP or the official ROM, it says success every time but the phone is still dead.
Could it be due to locked boot loader ?
Click to expand...
Click to collapse
Which rom did u flash, give the link please.
Are u sure it's for your version? It can be a broken file as well.
Does the device connects when u hold both volume buttons?
It's called emergency download mode, u can istall rom with miflasher.
There is a testpoint method also.
All u need is a pic from this post on http://4pda.ru/forum/index.php?showtopic=749580&st=700#entry51154086
U need to disconect battery, connect testpoint to battery and flash ur device with miflash.
After that let it charge, since this in your state phone consumes battery.
thanks for you answer, I flashed the MiMAXPRO EU ROM xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0.zip (sorry as a new user not allowed to post a link yet)
When I hold both volume buttons the screen is still black but MI Flasher works with COM10, after flashing a ROM or TWRP again MIFlash says "success" but the phone is still dead and won't start up even after holding power button for a long time.
I'm happy to open the phone and try the method on the russian forum, I will try tomorrow hope it will start up
agreusar said:
thanks for you answer, I flashed the MiMAXPRO EU ROM xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0.zip (sorry as a new user not allowed to post a link yet)
When I hold both volume buttons the screen is still black but MI Flasher works with COM10, after flashing a ROM or TWRP again MIFlash says "success" but the phone is still dead and won't start up even after holding power button for a long time.
I'm happy to open the phone and try the method on the russian forum, I will try tomorrow hope it will start up
Click to expand...
Click to collapse
Don't worry about your phone, the testpoint method will work for sure.
But in order to prevent this kind of situations ,we need to determine the reason how did it happen and you need to help me with that one by answering following questions:
1) You have mentioned that you had an error 1st time.
I also had error which was cache related, and it's OK because that partition was just formatted. You tried to flash again... but did you unmount your system partition for second time?
2) What's the capacity of your internal storage?
3) Did you use internal or external storage? If external then I need the model and the file system that have been used on that storage.
Doom Slayer said:
Don't worry about your phone, the testpoint method will work for sure.
But in order to prevent this kind of situations ,we need to determine the reason how did it happen and you need to help me with that one by answering following questions:
1) You have mentioned that you had an error 1st time.
I also had error which was cache related, and it's OK because that partition was just formatted. You tried to flash again... but did you unmount your system partition for second time?
2) What's the capacity of your internal storage?
3) Did you use internal or external storage? If external then I need the model and the file system that have been used on that storage.
Click to expand...
Click to collapse
Hello,
I managed to recover the phone, I installed a fresh windows 7 on another PC with only MI Flash Beta installed, device appeared as "Qualcomm HS-USB QDLoader 9008" as usual and I flashed the china ROM. Not sure why it wouldn't start previously after flashing, maybe issue with drivers.
1) unfortunately I don;t remember the syntax of the error, it was after a few seconds of flashing but the process seemed interrupted, I even googled it but my browser history has been purged.
2) 64GB (Helium)
3)I used internal storage, copied the zip on the phone using MTP.
Might try to go through the process again this weekend.
agreusar said:
Hello,
I managed to recover the phone, I installed a fresh windows 7 on another PC with only MI Flash Beta installed, device appeared as "Qualcomm HS-USB QDLoader 9008" as usual and I flashed the china ROM. Not sure why it wouldn't start previously after flashing, maybe issue with drivers.
1) unfortunately I don;t remember the syntax of the error, it was after a few seconds of flashing but the process seemed interrupted, I even googled it but my browser history has been purged.
2) 64GB (Helium)
3)I used internal storage, copied the zip on the phone using MTP.
Might try to go through the process again this weekend.
Click to expand...
Click to collapse
Well, I guess system was mounted and it gived u the error,but formatted it.
hi to all of you. I am very interested by this thread. Here is the story. I received my brand new mi max helium this week but it was the chinese rom. I am in France and my country did not appear in the settings. So I wanted to flash a global rom. I plugged it to my pc in recovery mode and a window appeared said that there is an update. I clicked ok and after a while I got stuck in the mi logo bootloop.
Then from then I tried everything possible from several solutions here, but nothing worked. What I got is the mi logo without bootloop, but nothing more.
I get the message that the bootloader is locked, but I can't get it unlock if it is in this state.
What I can reach is the recovery mode and the fastboot mode. But nothing else worked, flash or anything.
That is why I am interested to flash a recovery, in order to flash a clean rom, etc..
I did what you, Doom Slayer, explains, but I could not get a twrp flash. It ends with "receiving hello packet" in mi flash, and every thing stopped.
If I cannnot install any recovery, I cannot flash a rom.
So please if you have any suggestion, it would be helpful. Thanks a lot.
alain belay said:
hi to all of you. I am very interested by this thread. Here is the story. I received my brand new mi max helium this week but it was the chinese rom. I am in France and my country did not appear in the settings. So I wanted to flash a global rom. I plugged it to my pc in recovery mode and a window appeared said that there is an update. I clicked ok and after a while I got stuck in the mi logo bootloop.
Then from then I tried everything possible from several solutions here, but nothing worked. What I got is the mi logo without bootloop, but nothing more.
I get the message that the bootloader is locked, but I can't get it unlock if it is in this state.
What I can reach is the recovery mode and the fastboot mode. But nothing else worked, flash or anything.
That is why I am interested to flash a recovery, in order to flash a clean rom, etc..
I did what you, Doom Slayer, explains, but I could not get a twrp flash. It ends with "receiving hello packet" in mi flash, and every thing stopped.
If I cannnot install any recovery, I cannot flash a rom.
So please if you have any suggestion, it would be helpful. Thanks a lot.
Click to expand...
Click to collapse
Did you disable drivers signature?
Also some people have a better luck on windows 7, u can try a virtual machine.
If you can enter EDL mode, then you should be fine.
Unless Chinese already disabled it in a new update.
I would blame drivers. Make sure u got them correctly.
Updated tutorial.
Uploaded TWRP for helium, so you don't need to edit updater script anymore, since script will get correct model.
Now you can try to get root on your current rom and unlock bootloader without Xiaomi's confirmation.
People having helium with unlocked bootloader may also have problems installing roms from xiaomi eu, if they have TWRP from hydrogen.
You may update using my recovery.img from archive using fastboot, or TWRP(will also work for locked bootloader).
Doom Slayer said:
Did you disable drivers signature?
Also some people have a better luck on windows 7, u can try a virtual machine.
If you can enter EDL mode, then you should be fine.
Unless Chinese already disabled it in a new update.
I would blame drivers. Make sure u got them correctly.
Click to expand...
Click to collapse
hi Doom. Thank you for reply. But what do you mean by " disable drivers signature". I did not do anything but install the drivers and when I am on what I think is EDL mode(screen isi black) the driver is recognized as Qualcomm HS-USB QDLoader 9008(COM20).
Anyway, I will give another try and let you know. Thank you again.
---------- Post added at 09:14 AM ---------- Previous post was at 08:22 AM ----------
I followed your guide and I could get the twrp installed. So I tried to install rom(following your link). It said rebooting in 5 seconds, and then nothing. The screen is black, no power anymore, no logo, no vibes, and no life at all.
I cannot get any more reaction from it. I plugged it to my pc, but nothing is connected. I was so happy with twrp working... Any idea?...
one more information I don't know if it can help, when I flashed first, I tried the "xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0" and a message said "failed. This rom is for helium and this is hydrogen phone". Which is strange because mine is helium(4GB/128GB).
Then I tried with the "xiaomi.eu_multi_MIMAX_V7.5.6.0.MBCCNDE_v7-6.0" rom, and everything got ok, last message "success. The phone will reboot in 5 seconds", and from then, dead all over...
alain belay said:
one more information I don't know if it can help, when I flashed first, I tried the "xiaomi.eu_multi_MIMAXPro_6.8.4_v8-6.0" and a message said "failed. This rom is for helium and this is hydrogen phone". Which is strange because mine is helium(4GB/128GB).
Then I tried with the "xiaomi.eu_multi_MIMAX_V7.5.6.0.MBCCNDE_v7-6.0" rom, and everything got ok, last message "success. The phone will reboot in 5 seconds", and from then, dead all over...
Click to expand...
Click to collapse
Looks like you installed hydrogen TWRP and that caused all your problems.
I've been very careful to install the helium twrp from this thread...
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.