Related
Hello guys,
I hope you get not bored by these every day "I bricked my milestone" threads, but I do really need and would appreciate your help. So here is what's going on:
After Motorola delays the official 2.2 ROM again I decides to try CM6. I asked a friend, who has flashed his Milestone before, for an instruction and he gave me one.
I had an Milestone from O2 Germany with latest 2.36 update. First I made the recovery vulnerable. I downgraded to 2.34 and flashed the vulnerable-recovery only (of course the one for my 90.78 bootloader). I checked if the system was working right after every flash via RSD, and the phone bootet properly anytime. I applied the Androidiani update.zip and entered the OR. I wiped and applied the CM update via OR.
After I applied the CM update, the OR told me to reboot and so I did. I saw the Motorola logo and then the bootloader came up with an error message (Err:A5,70,39,00,27). I wanted to restore via Nandroid, but I no longer could enter the recovery (not to mention the OR). So I asked my friend again what to do and he told me to flash vulnerable recovery again via RSD (yes, I could enter bootloader mode) to be able to enter recovery again. After I flashed I could enter the recovery, but some new mad behavior appeared. The bootloader error disappeared, but every time I tried to boot, the phone ended up in boot loops (Motorola logo --> reboot --> Motorola logo --> reboot -->...).
Then I tried to restore via Nandroid. This seemed to work well, but after a reboot I got this bootloader error again.
To conclude:
flashing via RSD --> boot loops (recovery and bootloader work)
flashing via OR --> bootloader error (only bootloader works)
Some guy from android-hilfe.de told me to flash the bootloader, but I know this is very dangerous. So I went to the #milestone-modding irc-channel and asked for help. They gave me the advice to try to flash other sbf's, maybe an old 2.0. As I tried this today I got a new problem: the sbf file won't work. When I press 'start' in RSD everything starts as usual. But when the phone should show the message "sw update in progress" nothing happens and RSD get stuck on 0%. At the and I get the following message:
'ERROR: Flash failure: Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE003003F Command: ERASE (Error Code: e003003f)'
So I did not proceed. Anybody a suggestion what to do? I'm really helpless.
Greetings Luke
PS: the forum search lead me to this thread. The problem sounds pretty similar.
Try flashing a 2.1 sbf. Let me know what happens. Please use RSDlite v4.6 or higher
vladstercr said:
Try flashing a 2.1 sbf. Let me know what happens. Please use RSDlite v4.6 or higher
Click to expand...
Click to collapse
Good advice. Latest rsd and drivers. Try a different machine...rsd is moody. Try the GOT sbf, it includes the vuln recovery. I have had problems with Win7 that got solved with a different machine with xp.
If all of this does not work, we need to try fastboot. But try the rest first...
Sent from my Milestone using Tapatalk
Hey, thanks for your replie
I did this 3 hours ago. I used the full sbf for the 2.36 update for the German o2 Milestone. I also tried DACH and other versions before.
The result is always, that I end up getting boot loops like described above. RSDLite tells me the file is successfully flashed and unlike a 2.0 sbf the Milestone shows the message "sw update in progress".
I'm using RSDLite 4.9.
LukeTS said:
Hey, thanks for your replie
I did this 3 hours ago. I used the full sbf for the 2.36 update for the German o2 Milestone. I also tried DACH and other versions before.
The result is always, that I end up getting boot loops like described above. RSDLite tells me the file is successfully flashed and unlike a 2.0 sbf the Milestone shows the message "sw update in progress".
I'm using RSDLite 4.9.
Click to expand...
Click to collapse
Try a different version of RSDlite on a different machine or operating system.
Caz666 said:
Good advice. Latest rsd and drivers. Try a different machine...rsd is moody. Try the GOT sbf, it includes the vuln recovery. I have had problems with Win7 that got solved with a different machine with xp.
If all of this does not work, we need to try fastboot. But try the rest first...
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
You mean a GOT 2.1 or the 2.2 sbf?
Unfortunately I have no machine running XP at the moment. But I have a virtual XP running on my Win 7 Pro. But I guess it's no good idea to try to flash on this?!
LukeTS said:
You mean a GOT 2.1 or the 2.2 sbf?
Unfortunately I have no machine running XP at the moment. But I have a virtual XP running on my Win 7 Pro. But I guess it's no good idea to try to flash on this?!
Click to expand...
Click to collapse
There is no GOT 2.1
GOT is only 2.2. You can try GOT 2.2 sbf and RSD v4.6
Oh, okay =)
I thought there is a version by them.
Gonna try your advices and post the results.
Thank you so far
Wow, your problem still same me.
I was tried and solved:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
killed said:
Wow, your problem still same me.
I was tried and solved:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Click to expand...
Click to collapse
Did that before and tried it now. Didn't work for me. But thanks for your advice
I also flashed 2.2 from GOT. I was able to flash with RSD and it did not fail. But there is still the boot loop. So nothing changed.
This time I did it with my Atom-netbook and used RSD 4.6.
Ok, so I think I need to try something else. Only flashing with RSD easily doesn't work for me. Like I said in my post before: GOT 2.2 and the advice from killed did not work. Still getting boot loops.
So what would you recommend me to do?
LukeTS said:
Ok, so I think I need to try something else. Only flashing with RSD easily doesn't work for me. Like I said in my post before: GOT 2.2 and the advice from killed did not work. Still getting boot loops.
So what would you recommend me to do?
Click to expand...
Click to collapse
You tried GOT 2.2.1 sbf and it didn't work? Can you access recovery? There was a suggestion of fast boot, but I don't know what that is (just in case you wanted to google it or something, not sure). Do you have the drivers installed for your computer?
You could try this:
milestonefail said:
for some people RSDLite doesnt work properly. One way to fix that is put the SDL.bat file (attatched as .txt, change to .bat before using) in the RSDLite installation folder, move the .sbf file you are using to the same folder, and drag that .sbf to SDL.bat.
)
Click to expand...
Click to collapse
Read the end of this post: http://forum.xda-developers.com/showpost.php?p=11372663&postcount=51 Read the end
Also look here for the link for the drivers: http://forum.xda-developers.com/showpost.php?p=11163403&postcount=27
Good luck! I am not responsible if anything happens to your device.
Yep, it didn't work. RSD said the flash passed, but I always get boot loops. I can access th recovery, but even nandroid in OR doesn't work (I get back to that bootloader error I described in my first post).
I also don't know what fastboot is, but just using google won't help me, because I don't know, what I meant to do with fastboot.
The drivers are installed. Without them I guess RSD wouldn't even recognize my phone.
I also tried the batch file you posted, but it didn't work. I wasn't able to start the flashing process. I guess, the only thing the batch file does is to start RSD with admin rights.
These are all methods I tried and they just don't work. I need something different to this usual helpful stuff. That's why I posted in this forum, because I tried everything and I'm helpless at the moment.
Thanks for your advice anyway. I hope someone has a solution soon.
fastboot most likely will do nothing for you if a nandroid backup fails. Fastboot is a way to flash individiual partitions in case your recovery or nandroid does not work.
It works like adb (command line from a conected computer) and requires nothing on the phone. But if nandroid works...it will not do anything different.
Basically, a nandroid is a collection of .img files (one per partition) that a script flashes in sequence. With fastboot, you could flash all of the .img files from computer command prompt.
I would:
1) try a different nandroid...download the latest leak (01/25 from the dev forum). It is in nandroid format. I would factory reset the phone first.
2) if this does not work, i would fastboot erase and the fastboot flash (look up the syntax) every .img in the nandroid backup. This is just in case you OR is corrupted in some way...not likely, but i am out ideas.
Sent from my Milestone using Tapatalk
Hey,
thanks for your reply.
Your first recommendation would probably not work. I tried 4 different Nandroid backups and every time I get the bootloader error.
Basically I have no idea what fastboot is, where I get it from and not to mention how to get it work, so I think this is no option for me.
Right now I have resigned. Nothing seems to work. I consider getting a new phone. But before I do this I wanna ask you one last question: can flashing the bootloader theoretically effect anything? I think my phone IS bricked at the moment, so I'm not anymore afraid of flashing the bootloader. But if it would even theoretically be impossible, that this would change anything, then it's just a waste of time. So does flashing 90.78 bootloader via RSD Lite change anything?
Thank you!
LukeTS said:
Hey,
thanks for your reply.
Your first recommendation would probably not work. I tried 4 different Nandroid backups and every time I get the bootloader error.
Basically I have no idea what fastboot is, where I get it from and not to mention how to get it work, so I think this is no option for me.
Right now I have resigned. Nothing seems to work. I consider getting a new phone. But before I do this I wanna ask you one last question: can flashing the bootloader theoretically effect anything? I think my phone IS bricked at the moment, so I'm not anymore afraid of flashing the bootloader. But if it would even theoretically be impossible, that this would change anything, then it's just a waste of time. So does flashing 90.78 bootloader via RSD Lite change anything?
Thank you!
Click to expand...
Click to collapse
Why give up without trying? I believe you should flash it to see if it changes anything...How worse than this can it get?
Please...do not take my words for granted...Inform yourself from other sources before you try this...and if you do let us know if you successfully managed to get your phone back!
You misunderstood me. I wanted to try it, but if someone would have said that it's a waste of time, then I wouldn't have done it.
So I tried it, but flashing the bootloader (90.78 --> 90.78) didn't change anything. Still getting boot loops.
What do you think. Try a downgrade to 90.73? Is a downgrade even possible?
LukeTS said:
You misunderstood me. I wanted to try it, but if someone would have said that it's a waste of time, then I wouldn't have done it.
So I tried it, but flashing the bootloader (90.78 --> 90.78) didn't change anything. Still getting boot loops.
What do you think. Try a downgrade to 90.73? Is a downgrade even possible?
Click to expand...
Click to collapse
I dont think that is possible. I've read here on the forum somewhere that downgrading the bootloader is not possible...but you should search, maybe you find that it's possible.
Anyhows, I dont think your phone is lost, I just think we're missing something!
I also think it's not possible. I've read this in some forums, too.
It seems that it isn't lost. I was happy, as I found out, that I can enter recovery and bootloader. I thought it could easily be restored. But then nothing worked for me. So we must miss something, but I have no clue what.
What do you mean by:
"Then I tried to restore via Nandroid. This seemed to work well, but after a reboot I got this bootloader error again."
Are you sure you have enough battery?
You could try restoring a nandroid from other recovery. Replace the recovery from your sd-card. If you use Androidiani 3.3 try an older version of it or another OpenRecovery.
Hey,
I've got a problem with my Milestone, wich I upgraded to 2.2 Froyo and rooted. When I try to flash Roms in recovery mode. It says can't open /chache/recovery/command. I found a topic were a guy speaks of a problem with the RUU Rom. I don't know wich ruu rom i've got and where to find the one that works, I know that I need to be carefull with this due to the new security that disables rooting and that other thing...
Could someone please help this noob ;P
Greetings
If you are referring to the A853 milestone, you have to flash vulnerable recovery to enable you to run openrecovery, which is used to flash custom roms.
Sent from my Milestone using Tapatalk
And how do I do this?
I've tried RSD Lite with the sbf: vulnerable_recovery_only_RAMDLD90_78.sbf. Wich I got from Addictivetips in the post "how to root motorola milestone"
I didn't follow the procedure on the site for this problem. I just connected my Milestone A853 with laptop, through "Portal & Tools", selected the .sbf in RSD Lite ant started it up.
When it was done, turned my phone on again and used the button "x" and Powerbutton to open Recovery Mode. It still gave the error: Can't open /chache/recovery/command
Thanks for your help, I hope you've got a fix for this
Greets
DeMich said:
And how do I do this?
I've tried RSD Lite with the sbf: vulnerable_recovery_only_RAMDLD90_78.sbf. Wich I got from Addictivetips in the post "how to root motorola milestone"
I didn't follow the procedure on the site for this problem. I just connected my Milestone A853 with laptop, through "Portal & Tools", selected the .sbf in RSD Lite ant started it up.
When it was done, turned my phone on again and used the button "x" and Powerbutton to open Recovery Mode. It still gave the error: Can't open /chache/recovery/command
Thanks for your help, I hope you've got a fix for this
Greets
Click to expand...
Click to collapse
You don't want to have the phone powered on at all. Only in Bootloader mode when you want to flash via RSD Lite. Here's the best tutorial you can get: http://forum.xda-developers.com/showthread.php?t=983516
If you successfully flashed the vulnerable sbf, you still have to have open recovery prepared on the SD card.
Then at the "Can't open /cache/recovery/command" screen, you would select update.zip
If you get an error (EOCD error? I forget...) after selecting update.zip, that means you don't have vulnerable recovery.
If update.zip works and open recovery loads up... get flashing
I have two droid 3's and I rooted them both and went to install a blue theme on one of them from the rom manager app and it worked great, so I did it on my second one, too. When it was in the reboot process it never finished bootoing and it stopped at the red M. All it shows is the boot logo, not the boot animation. I have tried flashing it with rsd lite, but it always fails. Is there any other ideas as to what I should do?
You need to get rsdlite working(does it work on the other phone?). Get the drivers installed from motohelper (or reinstall) if needed, get the phone into ap fastboot and sbf to stock and go from there. Check this thread on users with the same issue.
Willis111 said:
You need to get rsdlite working(does it work on the other phone?). Get the drivers installed from motohelper (or reinstall) if needed, get the phone into ap fastboot and sbf to stock and go from there.
Click to expand...
Click to collapse
Yes, the theme works on the other phone. I will get the drivers and try again and will get back to you. Thanks for the help so far.
RaTTeDH said:
Yes, the theme works on the other phone. I will get the drivers and try again and will get back to you. Thanks for the help so far.
Click to expand...
Click to collapse
I meant rsdlite, have you ever used it with either phone without having an issue? I edited my previous post, added a link you might want to check out.
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
http://minus.com/mB0zknQrL/
I have never used RSDLite before. So I do not know if it works. But when I am flashing it with the stock 5.6.890 it fails at step 5. It reboots the bootloader. But it fails always at step 5. Let me try the other replys...
redsox985 said:
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
Click to expand...
Click to collapse
I have downloaded this and tried this. When I run the application moto.fastboot.exe it takes like 30 seconds and when I run the batcch file it immediately finishes and says moto fastboot is not recognized as an internal or external command, operable file or command. And finishes immediately. Sigh.
redsox985 said:
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
http://minus.com/mB0zknQrL/
Click to expand...
Click to collapse
The unbrick script will flash a vzw rom to your xt860 and have you stuck at the M logo anyways so I wouldn't suggest trying that. If you haven't used rsdlite before and are having trouble with it now you probably need to install the drivers from the motohelper software.
1./ download the drivers (from motorola)
2./ shutdown phone and turn it on by hold m + power
3./ select ap fastboot mode, enter and plug your phone into the computer ignoring any add new hardware
4./ start the driver install and follow it through
5./ unplug and replug your phone with computer leaving it fastboot mode.
Rsdlite should show your device under listed devices when you start it up at this point and allow you to flash w/e rom. I would suggest using the iucell or brazil retail fastboot files from the xt860 fastboot thread to get your phone up.
I fixed it using CMD in Windows flashing some stuff. Thanks guys!
Hi, my best friend she had a HD phone, one day got stuck into the M logo, the only thing I can do is get into the fastboot, no recovery no nothing.. So i try to reinstall the rom, have download several tools but i cant do anything, after several intents to install roms i hace in AP fastboot flash mode, device is unlocked status code 1fastbookt Reason sticky bit factoy_fastboot. for a 2nd time but i can install roms, I dont know if phone bootloader unlock and cant check... I dont know if phone is usb debugging cause it wont load the system. I dont see any internal files from phone I also try rsd lite, but the same it says that it start doing the process but nothing else happen.. any ideas on how to get a rom install there..
thanks
SAME thing..
Please do help us...No recovery...No debugging...stuck at logo..!!
If you don't have an unlocked bootloader, I don't think you can use Myth or RSD to flash an ICS rom over a JB rom.
Did you load the latest Motorola USB drivers? When you connect the phone, run adb to list the devices. Does your phone appear?
not for me doesnt show any devices... and while trying to do other commands always get stuck ad *daemond started succesfully* but doesnt do anything.. also when trying to use motorola device manager it says it will update and never connect to server and close the app.
if i do fastboot commands like reboot-loader it does work it reboots the phone, but if i try to flash something doesnt it doesnt do anything.. i try using mfastboot also and the same happen.
Is there a way to flash a rom or something so i can fix this phone or it is dead?
On the Fastboot screen, if it says UNLOCKED in capitals next to "Device Status:" , then this problem is easily fixable.
Download RSD Lite from here: http://forum.xda-developers.com/showthread.php?t=2231249
Download Motorola Stock Firmwares:
Stock Jellybean for AT&T: http://sbfdownload.droid-developers...MB886_NII_TA-2-16-release-keys-NII-MX.xml.zip
Stock Jellybean for Bell Canada: http://sbfdownload.droid-developers...FFW-11-4-release-keys-BellMobility-CA.xml.zip
Open up your zip file and replace the .xml with the new XML you will download from this link: https://www.box.com/s/num1eshkf0c2or2h4160 You really can't forget to do this!
Launch RSD, connect device to PC, make sure RSD recognizes it. Navigate to your firmware file, select it, and press the start button. Sit back, relax, and let it do its work. It will take around 5-10 minutes. Do not unplug the cable, and do not attempt if you are in a situation in which you think you may lose power (especially if running from a desktop PC).
If RSD Lite won't work, then this thread will show you how to manually flash your stock firmware: http://forum.xda-developers.com/showpost.php?p=40929335
Basically, you repeat all the instructions I just gave you and then manually input some lines in Command Prompt.
Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!