Related
Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !
jpearn said:
Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !
Click to expand...
Click to collapse
go finding a original recovery dump,and flashing it in fastbootmode.
Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.
1
californiarailroader said:
Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.
Click to expand...
Click to collapse
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.
lsnc said:
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.
Click to expand...
Click to collapse
Thanks! However, the US Version doesn't have an update for it, at least not yet, and I haven't been able to find a stock US A700 ROM.
So we would need to rename the install-recovery.old back to install-recovery.sh in /system as this was disabled in CWM ??
So has anyone managed to successfully put on the stock recovery ?? !!
jpearn said:
So has anyone managed to successfully put on the stock recovery ?? !!
Click to expand...
Click to collapse
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD
Moscow Desire said:
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD
Click to expand...
Click to collapse
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.
californiarailroader said:
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.
Click to expand...
Click to collapse
Sounds like a plan I'll keep things working for now, thanks !
jpearn said:
Sounds like a plan I'll keep things working for now, thanks !
Click to expand...
Click to collapse
View attachment updater-script.rar
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
I don't understand these instructions. What original file is being replaced? What update.zip are you referring to?
EDIT
Well, I tried to swap out the update script that came in the ROM: SDs_Acer_A700_AV043.RV00RC00_AV043.RV07RC04_EMEA_CUS1, with the one provided above and seemed to have made some progress...I put on an external SD card and renamed to update and then flashed it through the CWM recovery and it completed. A random offset was noted and then the SD update completed note. However, when I rebooted the device it stuck at the Acer logo and never went any further.
EDIT
So, it then occurred to me that the flash through CWM was probably only partially successful - maybe the replacement of the recovery worked. So, I took the same ROM I noted above, unmodified, placed on the external SD card, renamed, etc. and flashed it and it worked - I never saw any signs of CWM during this process. I hope this helps others too.
EDIT
Looks like I spoke too soon...the flash never got past a 1/4 of the progress bar. Looks like I still have a non-functioning device.
lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
Hi, I'm a A510 user. I used the CWM to wipe data/factory reset, after that i cant flash any zip, and even cant enter the system. When i turn on the tab, it stuck on 'iconia tab' LOGO, I tried to hard reset, then i got a 'Unrecoverable bootloader error (0x19000008)'
I enter the fastboot and flash the stock recovery back. next i use the recovery to flash update.zip as usual, but every time the flash will stuck in 1/5 of the whole progress bar, I changed it with other rom zip, or even change the SD card, it didn't work anyway!
every time the flash stuck in the same place of the whole progress bar, i guess it is not an accident! After read your solution, I check the script in my zip, then i delete 2 lines about 'format' command. I think this time will be ok! but to my surprise the green turtle fell down when flashing.
I think the idea is great, but it maybe make the script incomplete, so it cant be flash in.:crying:
Hello everybody i have a moto g XT1032 16 gb, bought on amazon. after unlocking bootloader and rooting my device, i used a guide on youtube (Convert Moto G (XT1032) to a Google Play Edition) to try the gp edition .... i updated to kitkat 4.4.4 and after that i received the update to lollipop 5.0.1, i updated it but now my device is stuck on bootloop
please someone help me!!
Can you give us more details?
Like if this is really a bootloop (in wich you would see that white image with an exclamation mark for a loooong time) or if you just can't switch your phone on?
I've read about it and, in a situation like yours, the phone usually bricks...
______________________________________
Edit:
When it happened to me, I did the following:
Download and execute the .bat of this topic after installing the phone drivers.
http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
After this, my phone went to the GPE but it could not flash an stock rom. Than, I did this:
forum.xda-developers.com/ moto-g/general/guide-moto-g-xt1033-android-5-0-lollipop-t2979623
Follow this steps exactly the way its written and it should work.
BobDiaz said:
Can you give us more details?
Like if this is really a bootloop (in wich you would see that white image with an exclamation mark for a loooong time) or if you just can't switch your phone on?
I've read about it and, in a situation like yours, the phone usually bricks...
______________________________________
Edit:
When it happened to me, I did the following:
Download and execute the .bat of this topic after installing the phone drivers.
forum. xda-developers. com/ moto-g/general/ guide-xt1033-downgrade-lollipop-5-0-to-t2969729
After this, my phone went to the GPE but it could not flash an stock rom. Than, I did this:
forum. xda-developers. com/ moto-g/general/guide-moto-g-xt1033-android-5-0-lollipop-t2979623
Follow this steps exactly the way its written and it should work.
Click to expand...
Click to collapse
Thanks for your reply, basically is stuck on the boot with the google logo and a lock unlocked that i think it's for the unlocked bootloader..And when I power off the device by pressing for a long time the power button, after 2/3 seconds it reboot automatically....
now i'll try with the guides you gave me! I hope it will works
------------------------------------------------------------------------------
Edit: I did execute the .bat file and it did work! Thank you so much! now,i can't understand the second link you gave me... do i have to do that process' or it's fine like this? and now if I download the lollipop update, am i supposed to have the same problem?
stechiocca said:
Edit: I did execute the .bat file and it did work! Thank you so much! now,i can't understand the second link you gave me... do i have to do that process' or it's fine like this? and now if I download the lollipop update, am i supposed to have the same problem?
Click to expand...
Click to collapse
When you say "it work", did you mean that you can boot normally or that you can flash any rom that you wish? Or you didn't try that? The second link helped me because I couldn't flash any rom except GPE's (the partition table of these are different). If you wish to revert to your stock rom, you'll need to do as the second tutorial said.
I am now with an 5.0.1 Lollipop running well.
Please, give-me a feedback of your situation.
:good:
BobDiaz said:
When you say "it work", did you mean that you can boot normally or that you can flash any rom that you wish? Or you didn't try that? The second link helped me because I couldn't flash any rom except GPE's (the partition table of these are different). If you wish to revert to your stock rom, you'll need to do as the second tutorial said.
I am now with an 5.0.1 Lollipop running well.
Please, give-me a feedback of your situation.
:good:
Click to expand...
Click to collapse
So, first of all, now I can only boot normally and use it as gpe 4.4.4... This morning I received the lollipo 5.0.1 update, I did it but when it was at half of the installation, it stopped and there was the little android with an "ERROR" message.. if you want I can attach a photo with the error, so you may know how to solve (I did it when I had the stock recovery)... Now I tried to flash a ROM, so I put the CWM and rebooted into recovery, but when I tried ti install zip from SD card it said me "error: can't mount /sdcard" (I had this problem already when I used the guide to convert into gpe) So now what I have to do? I would like to try Lollipop, and I would like also to be able to flash any rom whenever I want!
--------------------------------
Edit: I just attached a photo of the problem so may be you can understand what happens!
stechiocca said:
So, first of all, now I can only boot normally and use it as gpe 4.4.4... This morning I received the lollipo 5.0.1 update, I did it but when it was at half of the installation, it stopped and there was the little android with an "ERROR" message.. if you want I can attach a photo with the error, so you may know how to solve (I did it when I had the stock recovery)... Now I tried to flash a ROM, so I put the CWM and rebooted into recovery, but when I tried ti install zip from SD card it said me "error: can't mount /sdcard" (I had this problem already when I used the guide to convert into gpe) So now what I have to do? I would like to try Lollipop, and I would like also to be able to flash any rom whenever I want!
--------------------------------
Edit: I just attached a photo of the problem so may be you can understand what happens!
Click to expand...
Click to collapse
So, like I said above... Just follow the second link.
The first one give you a temporary solution. It main objective is restore the capacity of mounting the partitions and booting into /system.
The second one open your horizons again, letting you decide which rom you will install. Just follow this and you'll can feel the sweetness of the Lollipop!
DO NOT try to install ANY actualizations over the TEMPORARY GPE edition. If you want do go back to GPE, do the second tutorial before.
Gimme your feedback and click ThankYou if it was usefull!
Nice wood bench, by the way.
:good:
BobDiaz said:
So, like I said above... Just follow the second link.
The first one give you a temporary solution. It main objective is restore the capacity of mounting the partitions and booting into /system.
The second one open your horizons again, letting you decide which rom you will install. Just follow this and you'll can feel the sweetness of the Lollipop!
DO NOT try to install ANY actualizations over the TEMPORARY GPE edition. If you want do go back to GPE, do the second tutorial before.
Gimme your feedback and click ThankYou if it was usefull!
Nice wood bench, by the way.
:good:
Click to expand...
Click to collapse
Ok i'm downloading the necessary files ... just two last questions before I do this, cause i'll wait for your answer before starting doing everything... 1) Will I lose all userdata? obviously I'm going to backup my data but ... am I going to lose my file and data?
2) will it work even if my original software was Retail DE?
and finally, thank you for the help, I'm going to click thank you even if it doesn't work (hope not obviously ), cause you were very helpful
I've got the same problem after trying to convert my Moto G to Google Play Edition (worked fine up to 4.4.4), then I wanted to install Android 5.0.1 OTA and ended in the Reboot Loop.
I followed the first link and was able to get 4.4.4 working again. Then I tried to continue with the second link to get the chance to update later on 5.0.1, but everytime I wanted to run the command "mfastboot flash system system.img_sparsechunk.0" my Moto G in Fastboot alerts "File Size too large". Is there a way to get an 4.4.4 which enables me OTA Update to 5.0.1?
stechiocca said:
Ok i'm downloading the necessary files ... just two last questions before I do this, cause i'll wait for your answer before starting doing everything... 1) Will I lose all userdata? obviously I'm going to backup my data but ... am I going to lose my file and data?
2) will it work even if my original software was Retail DE?
and finally, thank you for the help, I'm going to click thank you even if it doesn't work (hope not obviously ), cause you were very helpful
Click to expand...
Click to collapse
Wel... The answers:
1) Yes. You'll loose all your user data. One of the steps during the installation of any room is erase all the cache partitions and the userdata. That way, you can prevent any compatibility issues.
2) You phone will "forget everything about it's past", and will "think" that it is Brazilian now. If you don't like it, try downloading an ADB compatible DE rom. But, in my opinion, the Lollipop is way better than the Kit Kat. Unless you need the Xposed Modules.
Cheers!
Merry Christmas! :laugh:
---------- Post added at 01:30 AM ---------- Previous post was at 01:19 AM ----------
redbull93 said:
I've got the same problem after trying to convert my Moto G to Google Play Edition (worked fine up to 4.4.4), then I wanted to install Android 5.0.1 OTA and ended in the Reboot Loop.
I followed the first link and was able to get 4.4.4 working again. Then I tried to continue with the second link to get the chance to update later on 5.0.1, but everytime I wanted to run the command "mfastboot flash system system.img_sparsechunk.0" my Moto G in Fastboot alerts "File Size too large". Is there a way to get an 4.4.4 which enables me OTA Update to 5.0.1?
Click to expand...
Click to collapse
Did you did everything like said in the tutorial? Well, if yes, I suggest trying to do as the first link before. That way, all the partition table will be in the correct place.
Give us a feedback!
Cheers!
@BobDiaz do you think i should also erase dalvik cache? because i do everything step by step but it does remain in bootloop with the google logo ....
Let me just understand:
Did you try the first tutorial again or you are in the second for the first time?
You ALWAYS need to erase your cache partitions. Doing a clean installation always prevent bugs and incompatibility issues.
I'll ask for photos again. Show me, if possible, the step-by-step; Or upload a video on youtube.
Cheers!
BobDiaz said:
Did you did everything like said in the tutorial? Well, if yes, I suggest trying to do as the first link before. That way, all the partition table will be in the correct place.
Give us a feedback!
Cheers!
Click to expand...
Click to collapse
Thanks for your answer! I tried to do everything as described, the first tutorial worked fine. Then I wanted to flash the Brazilian kitkat image image with fastboot like described in the second tutorial. While flashing the phone dropped the error notice "Image File Size too Large" while flashing system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2. I was able to finish the further steps but after rebooting the bootloader the Moto G was back in Boot Loop.
Can I do the second part of this tutorial (transfering moto g brazilian update to the phone and apply the update from sd card) also with the image of the first tutorial? How does this work?
redbull93 said:
Thanks for your answer! I tried to do everything as described, the first tutorial worked fine. Then I wanted to flash the Brazilian kitkat image image with fastboot like described in the second tutorial. While flashing the phone dropped the error notice "Image File Size too Large" while flashing system.img_sparsechunk.0, system.img_sparsechunk.1 and system.img_sparsechunk.2. I was able to finish the further steps but after rebooting the bootloader the Moto G was back in Boot Loop.
Can I do the second part of this tutorial (transfering moto g brazilian update to the phone and apply the update from sd card) also with the image of the first tutorial? How does this work?
Click to expand...
Click to collapse
Actually, you can't.
You can only apply UPDATES to the rom it was meant to be. You cannot apply an Lollipop Update made to an 4.4.4 Retail-BR to an GPE, even if it was an 4.4.4. It will bug the partition table, leading your device to bootloop.
If you've already tried to do as the second tutorial said more than one time, following all the steps, and it still is in bootloop, i recommend you to try searching for a alternative.
Give us the feedback anyway!
Cheers!
Here are some pictures of the error that occurs during flashing Kitkat 4.4.4 like it is described in the second tutorial.
Before, I launched the first tutorial and got a running 4.4.4 on my Moto G.
Image 1: State after entering "mfastboot flash system system.img_sparsechunk.0"
Image 2: Feedback on the Windows console after entering "mfastboot flash system system.img_sparsechunk.0"
Image 3: State after entering the last "flash system .. " command
redbull93 said:
Here are some pictures of the error that occurs during flashing Kitkat 4.4.4 like it is described in the second tutorial.
Before, I launched the first tutorial and got a running 4.4.4 on my Moto G.
Image 1: State after entering "mfastboot flash system system.img_sparsechunk.0"
Image 2: Feedback on the Windows console after entering "mfastboot flash system system.img_sparsechunk.0"
Image 3: State after entering the last "flash system .. " command
Click to expand...
Click to collapse
You may need to flash gpt.bin from 4.4.4 (it is in the 4.4.4 flashable). This will create a new correctly sized partition table.
Also, make sure you are using the mfastboot to flash (a.k.a motorola fastboot) and not the Google fastboot.
This is probably a partition table error.
Give us the feedback!
=]
________________________________________
I've seen this in other topic:
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884
BobDiaz said:
You may need to flash gpt.bin from 4.4.4 (it is in the 4.4.4 flashable). This will create a new correctly sized partition table.
Also, make sure you are using the mfastboot to flash (a.k.a motorola fastboot) and not the Google fastboot.
This is probably a partition table error.
Give us the feedback!
=]
________________________________________
I've seen this in other topic:
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884
Click to expand...
Click to collapse
I can't find the gpt.bin file, probably this is why i'm getting "image is too large" error... can you please explain to where i can find it??
stechiocca said:
I can't find the gpt.bin file, probably this is why i'm getting "image is too large" error... can you please explain to where i can find it??
Click to expand...
Click to collapse
I could not upload here in XDA the gpt.bin that I've used.
Try catching the one that comes with any ADB flashable rom (it is called "gpt.bin").
Try the stock from your country.
BobDiaz said:
I could not upload here in XDA the gpt.bin that I've used.
Try catching the one that comes with any ADB flashable rom (it is called "gpt.bin").
Try the stock from your country.
Click to expand...
Click to collapse
hey, how are you? i'm really happy because it finally worked! I just had to "mfastboot flash partition gpt.bin" to make it works and i didn't get the "image is too large" problem... now i'll do the second part of the second guide hope it will work!! thank you a lot @BobDiaz
Excellent.
Try the other tutorial and tell me how did it go.
@BobDiaz Now i'm currently running correctly lollipop 5.0 brazil en BR, am i able to install a custom recovery and flash any rom whenever i want?
Hello folks. Today I did a cache, system, data wipe in TWRP on my G920F. After that I tried to restore a nandroid backup, but it failed and when I tried to restart it said there was no OS installed. So the phone wouldn't boot. I figured I did something wrong so I downloaded a 5.1.1 stock rom (UK) and flashed it with odin. But after the flash the phone would just bootloop. How can I revive the phone? Tried flashing the firmware again using another version of odin and also, I did a factory reset from the stock recovery, but no dice. Any ideas? Thanks in advance
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Managed to make it work flashing another official rom, then factory reset. Lost all my files though...
Can be closed. Thanks!
Sent from my SM-G925F using Tapatalk
kendall1004 said:
Hey there,
check this thread here, should help (use TWRP to flash a ROM instead of Odin, links in thread).
Good luck!
Click to expand...
Click to collapse
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Immoblize said:
How can i make TWRP flash a rom when Galaxy S6 doesn't have SD card to put the rom in the phone?
Click to expand...
Click to collapse
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
kendall1004 said:
Connect the phone to your PC and copy the ROM file to its root folder (just open "phone" and drop it there).
Using TWRP's "install" menu, you can browse your files and point it to this one; usually you're already in the right directory.
Click to expand...
Click to collapse
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Immoblize said:
I wish that was so easy. I am on bootloop on my second day and i can fix it. I am getting crazy here. Nothing work - Kies, Smart Switch or Odin.
Click to expand...
Click to collapse
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Immoblize said:
THANKS A LOT for the info. I have today worked for about 8-9 hours to fix it. I will try read tomorrow on the site you put there and also read about how to put files to TWRP - since i don't have a SD card on my S6.
Click to expand...
Click to collapse
Sleep over it, tomorrow is another day
Also, browse my recent postings here; most of them revolving around your issue, this will surely help.
kendall1004 said:
None of these three will help, i'm afraid.
The bootloop issue is a result of system write protection with 5.1.1 version, the phone tries to override a flashed recovery-
if it succeeds in automatically rebooting after you flashed, you're stuck on bootloop.
You have to flash a new kernel and root user via Odin, then flash TWRP and use it to install a new ROM.
A short description in this thread here, have a look.
As long as you can get into download mode, don't worry, nothings bricked :good:
Click to expand...
Click to collapse
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Immoblize said:
Okay, i have done almost all of what you said.
But what im thinking about is the thread your refering to is to a S6 Edge and not for SM-G920F model.
But so far so good.
What kernel to you want me to flash? How can i root via Odin when i don't have USB-debugging on - But i can according to the thread, install SuperSU via TWRP.
I didn't know what kernel i had on, but i managed to install TWRP, install SuperSU via TWRP, pushing my stock rom to TWRP. But when installing the stock rom, it says "no md5 file found" or something like that. What am i doing wrong?
Click to expand...
Click to collapse
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
kendall1004 said:
Should work on both Edge and normal.
I have the G920F and did it this way, i also had problems, by the way:
http://forum.xda-developers.com/showpost.php?p=62550973&postcount=29
I recommend chosing an XtreStoLite ROM, the odexed version is an "improved stock" one, comes with a modified UniKernel and runs much smoother than stock.
Anyway, in TWRP, there is an option to skip md5 checking for backup files and for skipping the zipfile-check; not sure if you can also disable md5sum-checks.
Maybe you should try downloading the ROM from here or sammobile.de, verify the md5-sum yourself to make sure it is fine, and flash that one.
If TWRP doesn't think the ROM file is ok, it probably isn't ...
here's the odexed version of XtreStoLite:
http://forum.xda-developers.com/galaxy-s6/development/rom-xtrestolite-pure-edition-1-0-beta-1-t3082467
Click to expand...
Click to collapse
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Immoblize said:
Okay, i have flashed TWRP, installed the kernel and Super SU (http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866). But i can't flash the modem and bootloader for the XtreStoLite because it gives me Nand write error. I tried then to install XtreStoLite from TWRP which installed correctly but still doesn't fix the bootloop. I can read that i WILL get the bootloop if not using the correct modem and bootloader, but for some reason i am not able to flash them. Any help here? Or am i doing everything wrong here?
Click to expand...
Click to collapse
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. (...) Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
kendall1004 said:
Alright, you have root access and TWRP is running.
All you have to do is install the ROM file (unextracted, as a .zip) from your phone`s root folder; if your model is a G920F, the bootloader should be 5.1.1 and work, no need to change.
When exactly does Odin give you the error message, right after you click start or after a few secs of flashing?
I suspect the issue to be related to first reboot after flashing the recovery,.
When finished flashing TWRP, did you successfully boot into recovery menu be pressing vol up+home+power?
If you saw the bootloop screen then, you`ll have to do it again, i'm afraid:
I know, it`s annoying; but give it another try:
use Odin 3.1.0.7 (run with admin rights), do a full wipe and install TWRP 2.8.7.
When doing so and Odin gives you the "finished/successfully flashed" message, immediately press & hold the key combo to get into recovery; don`t wait for the scrteen to change or unplug the phone, you need to be damn quick here.
If you have done it right, you are in TWRPs recovery menu.
From there, install the XtreStoLite ROM after doing a factory reset; reboot and you should be fine.
Aaaarrgh we will get this thing running, goddammit
Click to expand...
Click to collapse
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
:silly:
Immoblize said:
What i did was install stock android via Odin.
Flashed TWRP
Flashed Alex V kernel first, then SUPER SU.
Flashed XtreStoLite and it still gives me bootloop.
What i can't manage to do is after flashing TWRP, then i am not fast enough to press Shutdown button, home button, and volume up button before the Samsung logo appears. I think that is the problem.
Click to expand...
Click to collapse
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
kendall1004 said:
:silly:
That IS the problem, i think :fingers-crossed:
Solved the same problem at reddit, take a look: reddit thread
Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it.
So now, take a deep breath, lean back and try again.
As soon as you have clicked to start the flashing procedure, press the 3 butons firmly, simultaneously and quick as lightning-
hold them down till it boots into TWRP.
Come on, even i have managed it after a few tries
Click to expand...
Click to collapse
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Immoblize said:
HMMM. I see.
It's not possible for me to boot into TWRP without the Samsung logo appears. I press the start, the same time i press the start, i press Power, Home and Volume Up button but still the logo appears. It takes 4 sec and it have flashed the TWRP. It's not possible...
Click to expand...
Click to collapse
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
Flash CF-Root for your model with Odin - Make sure you have an custom recovery installed (I advise you to use TWRP) (2.8.7.1 or newer REQUIRED for v.2.1 > of this ROM!!)
Click to expand...
Click to collapse
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
kendall1004 said:
So, for some reason you can't enter recovery mode.
This could be
a) TWRP is not installed correctly (did you use the .img ot the .tar-file? Odin needs the .tar-format: link )
or
b) the kernel you flashed doesn't work with this-
here is the one i have used to root my S6.
I would try to reflash above Unikernel first, if you used the .img-file of TWRP rather than the .tar to flash TWRP,
do it again with the .tar file instead.
If this fails, the last thing would be to flash a unmodified stock ROM to restore the original setup including the bootloader...
i will look into this now a little bit deeper, there has to be a workaround.
Best of luck for now, we stay in touch
EDIT: the developer of XtreStoLite recommends another way with Chainfire's root:
If the bootloader is your problem, you can update to the newest versions of bootloader and modem for your model following these instructions:
edgarf28`s instructions
I will do this right now, for a new version of XtreStoLite was just released today and i will upgrade.
Keep me informed
Click to expand...
Click to collapse
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Immoblize said:
I can enter the recovery mode (TWRP) but not before the Samsung logo appears when i install TWRP. I have tried many times and i still can't enter TWRP before the samsung logo appears for 1-2 secs.
I am not able to flash Edgar28s bootloader and modem because it always gives me nand write error fail. I think it's because i'm not rooted with CFautoroot - and to get rooted with that way, i have to have USB debuggin on which i don't have.
What i think is, that i was very close but i still can't manage to enter TWRP (after installing) without the samsung logo appears for 1-2 secs. Because what you said before "Unfortunately, you must flash TWRP again to try once more, as soon as the samsung logo apperars, your custom recovery is overridden and thats it."
So what do you think now?
And btw thanks for all the help so far. I'm trying my best and following your steps but i always think i'm very close. I'm also so close to destroy my phone but i've read so many places that "it's only a softbrick, that can be fixed very easy".
Click to expand...
Click to collapse
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed :fingers-crossed:
OK, so you can enter the TWRP menu and install a ROM, right?
Any stock ROM from sammobile.com includes firmware, kernel and bootloader, so flashing the right one of these should reset all this.
Give it a try, for i think TWRP is actually working- otherwise you wouldn't get to the screen.
If the phone runs again with stock firmware, you can then flash a custom ROM.
And yeah, we're close, this can be only a minor flaw...it's near impossible to brick your android phone, so they say.
Don't worry mate, and be assured you're not the only one:
i just got stuck on bootloop also for a few minutes after upgrading to the newest version of XtreStoLite, which came out today.
Using TWRP, i could just flash back the previous version and all's good again.
Cya tomorrow...
EDIT:
I read through your previous comments again; the "md5sum"- issue seems to be a problem with the ROM file itself (corrupted or wrong version).
I'd bet that flashing the correct stock firmware for your carrier and model will solve the problem.
So enter the exact model number (like G920FXXU3COI9 or such) you have, get the right ROM and flash it with Odin 3.10.7
I couldn't find a denmark carrier on sammobile, eventually you have to look here at XDA, there's a list of stock imges as well.
Read lots of threads around this issue, almost all solved the problem flashing a stock ROM again.
Fingers crossed
Click to expand...
Click to collapse
Yeah, i've never had problems entering TWRP menu. I can flash stock firmware via Odin but i can never do it via TWRP because it's says no md5 file found error - tho i can flash XtreStoLite (i think it's because it says aroma installer).
I've read many places about the md5 file error, but for some reason, i can't figure out how to fix it.
No, there is no Denmark model, but we have NEE (Nordic). The only stock firmware i can install is XEF (i don't remember where i got that from actually).
I will try agian and flash stock android via TWRP AND read about the md5 file error now/later. Tomorrow i will call the store i got the phone from and tell them i have a hardware issue or something like that. The guy owns a store for sellings covers, cases and stuff like that. He got the phone from Samsung free and sold it brand new in the package with 1 year warranty, so i will contact him tomorrow if i can't figure out how to flash stock android via TWRP or if it gives me error about the md5 file.
Talk to you tomorrow.
Update: I can not flash NEE model via Odin. Only XEF model - i also found out it was French firmware.
hey guys, yesterdy I got a notification for android 6.0 upgrade and it was a ~100mb file for preparation so i downloaded it and charged my battery and tapped to install it, it reboots and wants to start installing but then goes to recovery menu and gives an error
the phone is all stock, no root or bl unlock or anything
I attached the error msg below:
it's m8sd not e8sd, mistyped in topic
Might be due to bad zip file! Download the update again and try!
Kianush said:
hey guys, yesterdy I got a notification for android 6.0 upgrade and it was a ~100mb file for preparation so i downloaded it and charged my battery and tapped to install it, it reboots and wants to start installing but then goes to recovery menu and gives an error
the phone is all stock, no root or bl unlock or anything
I attached the error msg below:
it's m8sd not e8sd, mistyped in topic
Click to expand...
Click to collapse
I had a similar error as yours doing exactly the same thing but mine was a e8sw running LP5 Sense6 rooted stock with xposed.
Even when I uninstalled xposed and disabled supersu, I still could not install the upgrade.
Finally managed to get the upgrade by going all the way back to stock and allow the OTA updates all the way up the MM6 update. Took me nearly 2 days to do that.
I have taken clean twrp backups of all the stock updates and will try and post them here soon.
generalugh28 said:
I had a similar error as yours doing exactly the same thing but mine was a e8sw running LP5 Sense6 rooted stock with xposed.
Even when I uninstalled xposed and disabled supersu, I still could not install the upgrade.
Finally managed to get the upgrade by going all the way back to stock and allow the OTA updates all the way up the MM6 update. Took me nearly 2 days to do that.
I have taken clean twrp backups of all the stock updates and will try and post them here soon.
Click to expand...
Click to collapse
thank you for the information, but as I mentioned in op my phone is already all stock, I havent ever moded or rooted or anything, it's stock locked bootloader
Have the exact same issue. My device is compelitely stock. Tried flashing the recovery from the downloaded OTA but still got the sama error. Hopefully someone will be able to resolve the issue.
if you have problems in installing OTA updates, follow these steps
1. check if your CID and MID are matching each other. they should be both for same region. mine are for vietnam. mec_dugl / HTC__057
2.Flash an stock RUU from http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
3.Skip all registeration process and directly go to update menu.
4.this is a 3 stage update process: a small update for some applications/another 100 MB update for making device ready for main update!! / at last 1 GB main update . each one should be downloaded and installed separately.
5. after downloading 100MB update, DO NOT restart. coneect your phone to PC and go to download folder on phone internal memory, there should be a zip file containing updates(sadly I forgot file name), copy it on your PC and extract recovery.img from it.
6. boot your phone into bootloader and flash stock recovery you've extracted using fastboot.
7. now you have complete stock ROM. go to setting/update again and follow update process.
8.after updating you may flash twrp and supersu.
9. I don't know why, but there is a good chance that after messing with system files in MM you get stuck in several kinds of bootloops and soft-breaks. Don't worry; all you should do is going to recovery and wiping caches. sometimes you need a factory reset too. also have in mind that a complete boot after changing system files may take up to 15 minutes even without wipes.
@sam5154 well thank you for the info, Im gonna try these steps except, I will try to download again and flash recovery and try it before flashing a RUU and lose everything
but I hope it works anyway, btw mine is also vietnam region.
sam5154 said:
if you have problems in installing OTA updates, follow these steps
1. check if your CID and MID are matching each other. they should be both for same region. mine are for vietnam. mec_dugl / HTC__057
2.Flash an stock RUU from http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
3.Skip all registeration process and directly go to update menu.
4.this is a 3 stage update process: a small update for some applications/another 100 MB update for making device ready for main update!! / at last 1 GB main update . each one should be downloaded and installed separately.
5. after downloading 100MB update, DO NOT restart. coneect your phone to PC and go to download folder on phone internal memory, there should be a zip file containing updates(sadly I forgot file name), copy it on your PC and extract recovery.img from it.
6. boot your phone into bootloader and flash stock recovery you've extracted using fastboot.
7. now you have complete stock ROM. go to setting/update again and follow update process.
8.after updating you may flash twrp and supersu.
9. I don't know why, but there is a good chance that after messing with system files in MM you get stuck in several kinds of bootloops and soft-breaks. Don't worry; all you should do is going to recovery and wiping caches. sometimes you need a factory reset too. also have in mind that a complete boot after changing system files may take up to 15 minutes even without wipes.
Click to expand...
Click to collapse
Hi, thanks for this. I will try this once i got home.
But i have one questions, mine is Vietnam MEC_DUGL with stock lollipop 5.0.2. The RUU only available for stock lollipop 5.0.1. Can I use this RUU or should I look for specific RUU for lollipop 5.02?
Thanks!
Kianush said:
@sam5154 well thank you for the info, Im gonna try these steps except, I will try to download again and flash recovery and try it before flashing a RUU and lose everything
but I hope it works anyway, btw mine is also vietnam region.
Click to expand...
Click to collapse
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
sam5154 said:
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
Click to expand...
Click to collapse
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Kianush said:
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Click to expand...
Click to collapse
Have you tried the suggestion above? Let me know the result! Thanks man
sam5154 said:
If you gonaa try that, then remeber to unroot and uninstall xposed, and you can use titanium backup for restoring your apps and data of course.
Click to expand...
Click to collapse
and how to check for this mec_dugl / HTC__057?
the first part is ok it shows that in booloader menu, but how to check for HTC__057??
Kianush said:
in op I already told that I dont have root or anything and the phone is all stock and it was like this from the begining, that means no xposed or anything else
Click to expand...
Click to collapse
Kianush said:
and how to check for this mec_dugl / HTC__057?
the first part is ok it shows that in booloader menu, but how to check for HTC__057??
Click to expand...
Click to collapse
Here you go :
If you want more information, use ADB (if you don't how to get it going, use the search on the forum or Google about it).
While you phone is connected to your PC, type adb reboot bootloader and wait for your phone to reboot into bootloader mode. Once there, you can perform fastboot commands like getvar. Type fastboot getvar all and you will see all the information about the phone, including the product variable which lists the model you have.
Source : http://forums.androidcentral.com/htc-one-m7/320871-how-check-htc-one-variant-model.html
bataskhayal said:
Here you go :
If you want more information, use ADB (if you don't how to get it going, use the search on the forum or Google about it).
While you phone is connected to your PC, type adb reboot bootloader and wait for your phone to reboot into bootloader mode. Once there, you can perform fastboot commands like getvar. Type fastboot getvar all and you will see all the information about the phone, including the product variable which lists the model you have.
Source : http://forums.androidcentral.com/htc-one-m7/320871-how-check-htc-one-variant-model.html
Click to expand...
Click to collapse
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Kianush said:
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Click to expand...
Click to collapse
Yes bos, i also did the recovery trick but still cant make it work. So the only solution we havent try is to flash RUU which i doubt also will make it work since my phone also factory stock. So i guess will stay in 5.0.2 for a while.
Kianush said:
Thank you for the info
btw I did go through the steps of downloading the 110mb update and flashing its recovery before pressing install and that didnt work and still gives OP error
so I guess I have to use RUU but not gonna do that for a while and also Im not so sure it'll work because the phone is already factory stock!
Click to expand...
Click to collapse
Hi, I have managed to finally update my Vietnam HTC One E8 dual SIM (MEC_DUGL) to Android 6.0. The problem that cause the error is the error recovery file, hence I re-install the RUU to get the correct recovery.img file. Below are the steps :
Note : Try with your own risk
1. My device is currently stock 5.0.2 no root and locked. Before starting the update process please make sure to backup all of your important data. Im using the stock HTC backup software, when you restore your device after you finished your update process, it will re-install your currently installed apps , contacts, settings, etc.
2. Download RUU for your device here : http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
I downloaded :
[Vietnam][DUAL][M8sd][mec_dugl][CID HTC__059][OPAJ20000] :
[Lollipop 5.0.1][2.35.425.2] : LINK
Seems not match with my current software (5.0.2), but eventually it will do the magic.
3. Flash RUU. NOTE : You will lose all of your data in your internal phone memory. Make sure to backup all of your important files.
Steps:
1) Download RUU.
2) Rename RUU to 0PAJIMG.zip (the first character is a zero, NOT A LETTER O)
3) Put renamed 0PAJIMG.zip on your external_SD
4) Boot into your bootloader and make sure your in hboot and let it update its RUU.
5) No PC, no adb, no fastboot, no terminal is needed, just a root explorer to rename and transfer the renamed RUU file to external_sd
6) After you have updated your RUU, make sure to remove the 0PAJIMG.zip from your external_sd because it will ask to update your RUU everytime your reboot to your bootloader which it is technically supposed to do but its unnecessary after you have done it once (unless you are planning on flashing RUU again).
7) Done!
Source : http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210
4. Reboot your phone, now your phone is back to factory stock, connect it to wifi, no need to set up any account, just go directly to software update from Settings > About > Software Updates. Just install all the available software updates (5.0.2 > 6.0 part 1 > 6.0 part 2).
5. BOOM! Your HTC One E8 now runs Android 6.0.1 Marshmallow.
6. Restore your phone from the stock HTC Backup Software.
7. Done
Unbrick tool by One-Team - EypCnn
First: This tool seems to be from EypCnn, One-Team. All credits to them!
EDIT2: I no longer own this device, so i will leave this thread here for people to use. But don't expect any direct support from me .
What can this tool do?:
Restore phone to Stock(International) Firmware (S048) Marshmallow (Locked & Unlocked bootloader)
Fix Lost or bad Signal / IMEI any software Problem
For who does this work?
Pretty much any Lenovo P2 Variant (Chinese and International)
Phones which can access bootloader(you have to boot into it)
Works on Locked & Unlocked Bootloader
Installation aka. Flashing-Steps
Put your phone into bootloader (which is also fastboot) mode.
Download the folder and unzip it.
Connect your phone to your pc.
Go into the unzipped folder and open "flashall - stock reco.bat"
Wait, for the process to end, your phone will reboot on its own.! A stock lenovo bootlogo will show up !
You can disconnect your phone cable from pc and plug into a wall charger, just to be safe. Once the lockscreen is showing up, you're done.
If you want to flash Custom Roms:
look below:
WHEN MOVING TO CUSTOM ROMS NOW:
1. Boot to twrp. (Make sure it is pietwrp from telegram or the official 3.2.3 or later version)
2. Select WIPE menu option
3. Select data partition
4. Change file format to f2fs or anyother.
5. Go back to Start Menu of TWRP, choose Reboot Menu Option
6.Reboot to Recovery
7. Repeat Steps 2 and 3
8. This time select EXT4 when changing file format
9. Do Step 5 and 6
10. Wipe System,Cache and Dalvik-Cache partitions
( for older twrp versions: 10.1 If you're on official twrp 3.2.3 or lower, you have to flash pietwrp or latest twrp now !)
11. Flash your Custom Rom, Gapps (optional) and latest Magisk(optional)
12. Wipe Cache and Dalvik-Cache
13. Reboot. First Boot might take a few minutes but never longer than 7minutes.
If it takes longer, you're encounter a so called bootloop.
Comment hear if that happens, containing information on your twrp-version, rom, gapps, magisk and mods(if present) you're using.
When you corrupt your internal Storage or geht TWRP Error 1001, Error 7:
1. Repeat steps 2-6
2. Repeat steps 7-8
Download(Official Link)
2nd Link(reuploaded because some couldn't download it from androidfilehost): https://drive.google.com/open?id=1wUOZiTwW8mo0IheAGONyj9-QnjimnY2M
I will help if questions arise.
Credits to One-Team & EypCnn.
Thanks a lot. You literally saved my life!
Works like Magic
Thanks a lot for saving my ass . simplest way to downgrade to mm too. Thanks again
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
eried1 said:
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
Click to expand...
Click to collapse
My p2 was bricked and , stuck in boot loop. I followed the above instructions, 10 mins into it , it booted with mm version, the same version when i bought and booted for 1st time. It was like a new phone to me.
So i assume if one has upgraded to noughat and want to downgrade but is worried he might brick his device, one can take a back up and try this tool. It works flawless.
No harm in trying this one if ur p2 can boot up mate. Give it a shot. Good luck
Cheers
This tool has saved my device from multiple over a span of two years soft bricks. Can confirm it to do wonders.
eried1 said:
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
Click to expand...
Click to collapse
THis will solve your problem , Cheers.
I tried but cannot download it - do you where to find it?
can i flash this without pc?? if yes please tell how
@sm00th4f3 bro, i wanna know, does this tool flashes full ROM including modem files etc, even on unlocked bootloader?
What is the state of bootloader after using this tool?
amansehdav said:
@sm00th4f3 bro, i wanna know, does this tool flashes full ROM including modem files etc, even on unlocked bootloader?
What is the state of bootloader after using this tool?
Click to expand...
Click to collapse
It flashed everything you have when you buy a new phone. And no, it doesn't lock your bootloader.
So you can either :
- keep using MM Stock Rom S048
- Update via ota in System like you normally would do.
- Update till latest Firmware, then flash twrp- and then Custom Rom of your Choice.
Bootloader is in the same state it was before you used this tool.
sm00th4f3 said:
It flashed everything you have when you buy a new phone. And no, it doesn't lock your bootloader.
So you can either :
- keep using MM Stock Rom S048
- Update via ota in System like you normally would do.
- Update till latest Firmware, then flash twrp- and then Custom Rom of your Choice.
Bootloader is in the same state it was before you used this tool.
Click to expand...
Click to collapse
So how does it fixes corrupted modems? it cannot be flashed on unlocked P2 right?
amansehdav said:
So how does it fixes corrupted modems? it cannot be flashed on unlocked P2 right?
Click to expand...
Click to collapse
I literally just answered it above somewhere.
(Literally in thread description)
You can flash it on unlocked bootloader or locked as well.
So many thanks for bringing up tis tool for us!
This thread should be stick as the "New user" thread is, they definitely belong together.
Download source
Thanks guys, if this works I can now revive my phone. But can someone please upload the tool to another place like google drive. From android filehost it will take an eternity to download!
HkQc said:
So many thanks for bringing up tis tool for us!
This thread should be stick as the "New user" thread is, they definitely belong together.
Click to expand...
Click to collapse
I didn't bring it up, i just linked it . All Credits belong to ONE TEAM and EypCnn.
ryd3r89 said:
Thanks guys, if this works I can now revive my phone. But can someone please upload the tool to another place like google drive. From android filehost it will take an eternity to download!
Click to expand...
Click to collapse
Link updated, Cheers
Lavesh05 said:
can i flash this without pc?? if yes please tell how
Click to expand...
Click to collapse
Nah you need a Computer for this.
no signal after using "flashall - stock reco.bat", it finished successfully, but after rom setup still no signal
GPSSlovakia said:
no signal after using "flashall - stock reco.bat", it finished successfully, but after rom setup still no signal
Click to expand...
Click to collapse
If you used some other tool for imei. You are pretty much done for.
Using this tool i can go to MM version and can upgrade to S251. However after installing twrp and flashing custom rom, it goes to bootloader