Related
To clean up another thread, I open this one to continue:
chipzter said:
I used the mempodroid exploit so I didn't need to install a custom recovery to root it.
It freezes and shows the acer-logotype and it shows the following text in the upper left corner:
Bootloader Version 0.04.04-ICS-MDRR (Unlock Mode)
So not totally dead. But definitely not completely alive either....
Do you think it would be OK to make a new thread with my problem? It would be nice to keep the discussion public so that it can help other people if they get the same problem...
Click to expand...
Click to collapse
@ Chipzter
Which language-firmware does you need? Because Acer has different FW versions for diff. countries?
First of all, download from Acer a Full Firmwareversion of your choise ( or country) from here
http://global-download.acer.com/Step5.aspx?Step1=Tablet&Step2=ICONIA%20TAB&Step3=A510&BC=Acer&SC=&LC=en&OS=a09&FS=O02&Category=OS
The file must be have a little bit more as 300MB.
* Open the archiv. You'll find a pdf and a file "update.zip" in it. Follow the instruction: copy the file update.zip to the root od the external SD card and start the Tab with the Key-Kombo, which is written there.
? Does it works? What it happen? What does you see?
You can try this a few times, it doesn't matter. Pls give attention, that your Accu has as min. 50%, or after that the TAB start to flash, connect the power-supply during the flash-phase. If you want to repeat, disconnect first at all, the power-supply; if the Tab start to flash, connect the power again.
Pls write the result here, don't try anything with Flashboot at this time or other things.....
Wesie said:
Which language-firmware does you need? Because Acer has different FW versions for diff. countries?
Click to expand...
Click to collapse
I don't know exactly. It was ordered online in Sweden, but from a company that sends everything from France. Still I think it was the same version that's generally available in Swedish stores. I had the language set to English though, because I'm more comfortable with English operating systems.
Wesie said:
First of all, download from Acer a Full Firmwareversion of your choise ( or country) from here
(...URLS removed since I don't have permission to post URLs yet...)
The file must be have a little bit more as 300MB.
Click to expand...
Click to collapse
Since the device never booted properly after the failed OTA update, I wasn't sure which firmware version I had. I tried the following ones:
EMEA.CUS1
WW.GEN1
EMEA.DE
EMEA.GB
All of them had file sizes over 300Mb.
No matter which one I tried, It always showed me the green android with a spinning icon for about 0.1 second, then it showed a lying down android with a red exclamation mark and nothing else happened. And I tried many times. But this was before my failed rescue attempts with flashboot.
Wesie said:
* Open the archiv. You'll find a pdf and a file "update.zip" in it. Follow the instruction: copy the file update.zip to the root od the external SD card and start the Tab with the Key-Kombo, which is written there.
? Does it works? What it happen? What does you see?
You can try this a few times, it doesn't matter. Pls give attention, that your Accu has as min. 50%, or after that the TAB start to flash, connect the power-supply during the flash-phase. If you want to repeat, disconnect first at all, the power-supply; if the Tab start to flash, connect the power again.
Click to expand...
Click to collapse
Now I'm unable to enter the recovery mode at all. the key combination has no effect and it always stops at the green acer logo and the Bootloader version message.
Ok, maybe the language check failed.
1- Take the update.zip file and unzip it to a folder.
2- Go to folder "\META-INF\com\google\android"
3- Edit the updater-script and put a # as first character of first line. This will avoid this line to execute: #assert(getprop("ro.product.name") == "a510_...");
4- Zip all files again and name it update.zip.
Copy the zip to the root and try the key-combo once again ( without Power-supply) . Reconnct the power, if the tablet start to flash.
I just tried it and it didn't work.
My problem is that the recovery doesn't even start. I think I need to get the recovery partition working before updating using the update.zip method will work.
Hard issue ...
OK - let's try to activate the Stock-Recovery:
* Download the stockrecovery from here and save the *.img file in the same directory, where your adb / fastboot.exe is available
Switch the board on with following procedure:
> press the Volume+ Key (2 Dots) + Power and switch the Screen Lock few times on / off
with this prcodure you should go into the Fast-Boot-Mode.
Here you can flash the Stock-Recovery:
> fastboot flash recovery <name of the image.img>
If the flash-process is finish
> fastboot reboot
stahai Andrea
Wesie said:
* Download the stockrecovery from here and save the *.img file in the same directory
Click to expand...
Click to collapse
Hmm.. I didn't see any link to the stock recovery. I did find one in the CWM thread called recovery_1_044_00.img and tried to flash that to recovery. The good news: I'm still able to enter fastboot mode and flashing doesn't give me any error. The bad news: It didn't help. I'm still unable to enter recovery mode even after flashing the stock recovery.
erihed claim
chipzter said:
Hmm.. I didn't see any link to the stock recovery. I did find one in the CWM thread called recovery_1_044_00.img and tried to flash that to recovery. The good news: I'm still able to enter fastboot mode and flashing doesn't give me any error. The bad news: It didn't help. I'm still unable to enter recovery mode even after flashing the stock recovery.
Click to expand...
Click to collapse
try the attached stock recovery.img (6.0 MB)
good luck
The good news: I'm still able to enter fastboot mode and flashing doesn't give me any error.
Click to expand...
Click to collapse
OK, first step is done.
If you've flashed the stock-Bootloader, than you can try once again to update the Tablet with the update.zip from the external-SD Card (a description pdf should be already available in the file, which you've download from the Acer-Homepage)
Please ensure, that the update.zip contains a full image ( file-size over 300MB ) and for sure, please disable the language flag.
If you need some help to modify the one line in the script, give me a small hint, I'll make it for you and give you the DownLoad-link.
If the flashprocess ist finish , without any errors, you must only reset your data ( in this case, I'll prefer to use the scenario via Reset-Button)
is it possible you are on jelly bean?
in this case the combination to enter the recovery is:
Power and Vol ** after first vibration release the power button after second vibration release the ** button and press *
@Paulinche
is it possible you are on jelly bean?
in this case the combination to enter the recovery is:
Power and Vol ** after first vibration release the power button after second vibration release the ** button and press *
Click to expand...
Click to collapse
The bootloader is the "old" one (ISC), and I think, that this combination is the new key-stroke for the CWM. If Chipzter try to reanimate the Tab with the org. Stock-SW, so that he can make, after successful flashing the tab, reset the UserDate and booting normal, the online-update:laugh:
Ok, let's start from scratch. Ground zero so to speak.
I'd like to know what bootloader you are running now. ICS or JB?
Reason is, that the recoveries, stock or CWM, must match the bootloader version, because they contain the specific Boot kernel. You can not mismatch these, or nothing's going to work. Not a Rom,not an update.
If you have ICS bootloader, you must have either a stock ICS Recovery, or an ICS CWM.
If you have a JB bootloader, you must have JB stock recovery, or JB CWM.
You can fastboot flash a stock ICS or JB recovery (stock or CWM), then you are able to flash stock roms or custom roms. But they must match, or you're just pissing in the wind.
So what be 'Ye Matey?
MD
If he use the bootloader from the Link, this is the BL from ISC.
Also the SW form the Acer-Server is ISC. So it should match. On other hand: The FW from Acer flashed also the BL to the right version (in recovery mode)
If his Tablett is starting ( maybe with or without Reset of the User-Data), he can use the normal updates via WLAN ( 1st there come an update for ISC, the 2nd update to JB.).
But i this moment, he must bring back to live his Tab....
For sure, I let him not go over the CWM, because something was going wrong, and a "one click tool" was used, after that some partitions was formated and if someone flashed the CWM, he should know, what he do --- here I want minimize the risk.
So I try to give him a hand to bring the Tab back to live with the stock FW, because with CWM, there can be going something wrong. Uncomfortable we're living not in the same country and I have not the Tab in front of me ...
Paulinche said:
try the attached stock recovery.img (6.0 MB)
good luck
Click to expand...
Click to collapse
Thank you for posting that .img file! Unfortunately, I still have no luck initiating the recovery process, even though fastboot seems to succceed:
$ ./fastboot flash recovery recovery.img
sending 'recovery' (6144 KB)...
OKAY [ 1.554s]
writing 'recovery'...
OKAY [ 1.472s]
finished. total time: 3.026s
I would expect (but really have no idea) that if I have a working boot loader (which seems to be the case for me) it should be enough to flash the correct recovery partition to be able to boot into recovery mode. But maybe it depends on data in some other partition like BOOT or SYSTEM. (I'm assuming that the boot partition doesn't contain the boot loader, but just the kernel and RAMdisk for booting the OS contained in SYSTEM)
I've probably messed up both BOOT and SYSTEM in my desperate efforts, but in my defence ( ) my first attempt to flash a new recovery (both stock and custom) failed somehow since the original stock recovery got reflashed automatically on boot even using the correct key combination.
---------- Post added at 01:26 AM ---------- Previous post was at 01:16 AM ----------
Moscow Desire said:
Ok, let's start from scratch. Ground zero so to speak.
I'd like to know what bootloader you are running now. ICS or JB?
Click to expand...
Click to collapse
Hi MD! Thank you for taking the time to reply! I'm really moved by the willingness of people here to try and help me out!
The tablet was running ICS before the meltdown. I was attempting to do an over-the-air update but it froze at around 80% (if memory serves) and I finally had to reboot at which point it got stuck at the "ICONIA TAB" logo after the olympic animation sequence.
I take it that the bootloader is still from ICS since the following text is displayed when trying to boot now:
Bootloader Version 0.04.04-ICS-MDRR (Unlock Mode)
---------- Post added at 01:34 AM ---------- Previous post was at 01:26 AM ----------
Wesie said:
OK, first step is done.
If you've flashed the stock-Bootloader, than you can try once again to update the Tablet with the update.zip from the external-SD Card (a description pdf should be already available in the file, which you've download from the Acer-Homepage)
Click to expand...
Click to collapse
I may be wrong, but I think I've flashed the recovery partition, not the boot loader. I read somewhere that you can't flash the boot loader over USB without using nvflash and that something necessary for that to work on A510 is still not publicly available.
In any case, the recovery still won't start. The device still freezes at the boot loader version message.
By the way, I also tried an older version of the CWM recovery image (6.0.1.4) that I think was ICS compatible.
chipzter said:
Thank you for posting that .img file! Unfortunately, I still have no luck initiating the recovery process, even though fastboot seems to succceed:
$ ./fastboot flash recovery recovery.img
sending 'recovery' (6144 KB)...
OKAY [ 1.554s]
writing 'recovery'...
OKAY [ 1.472s]
finished. total time: 3.026s
I would expect (but really have no idea) that if I have a working boot loader (which seems to be the case for me) it should be enough to flash the correct recovery partition to be able to boot into recovery mode. But maybe it depends on data in some other partition like BOOT or SYSTEM. (I'm assuming that the boot partition doesn't contain the boot loader, but just the kernel and RAMdisk for booting the OS contained in SYSTEM)
I've probably messed up both BOOT and SYSTEM in my desperate efforts, but in my defence ( ) my first attempt to flash a new recovery (both stock and custom) failed somehow since the original stock recovery got reflashed automatically on boot even using the correct key combination.
---------- Post added at 01:26 AM ---------- Previous post was at 01:16 AM ----------
Hi MD! Thank you for taking the time to reply! I'm really moved by the willingness of people here to try and help me out!
The tablet was running ICS before the meltdown. I was attempting to do an over-the-air update but it froze at around 80% (if memory serves) and I finally had to reboot at which point it got stuck at the "ICONIA TAB" logo after the olympic animation sequence.
I take it that the bootloader is still from ICS since the following text is displayed when trying to boot now:
Bootloader Version 0.04.04-ICS-MDRR (Unlock Mode)
---------- Post added at 01:34 AM ---------- Previous post was at 01:26 AM ----------
I may be wrong, but I think I've flashed the recovery partition, not the boot loader. I read somewhere that you can't flash the boot loader over USB without using nvflash and that something necessary for that to work on A510 is still not publicly available.
In any case, the recovery still won't start. The device still freezes at the boot loader version message.
By the way, I also tried an older version of the CWM recovery image (6.0.1.4) that I think was ICS compatible.
Click to expand...
Click to collapse
Remember that the sequence to boot to stock recovery, is different in ICS than the sequence steps for JB. I guess this changed with the release of JB. Honestly, can't remember how to boot to recovery on ICS (I always use adb, but that won't work for you.) At least on the 700 it did.
If the recovery.img flashed successfully, then there's no reason why you shouldn't be able to boot to it. Don't know the sequence for the ICS 510, but on the A500, it was vol- and pwr.
Another idea, is to see if anybody has a boot.img, system.img and flexrom.img for ICS. Then you can simply fastboot it.
As with the bootloader, it's correct. You have to use NVFlash to flash the .bin. You can however, flash a bootloader.blob via CWM though. I helped a person last month get his tab straight using that method.
MD
I still have no luck initiating the recovery process
Click to expand...
Click to collapse
Does you've follow the instruction which Acer attached?
If the original update.zip failed in the beginning, you must modify the first line in the update.zip [add a # in front; thats all]
META-INF\com\google\android\updater-script
First line is simular :
Code:
assert(getprop("ro.product.name") == "a510_ww_gen1");
change it to
Code:
#assert(getprop("ro.product.name") == "a510_ww_gen1");
Please give an attention, that you does not make the change with a normal Windows-Editor ( diff. CR&LF ). PLease use Notepad++, Textpad or a simular editior...
Another idea, is to see if anybody has a boot.img, system.img and flexrom.img for ICS
Click to expand...
Click to collapse
I have all 3 files (German) from my Tab, after CWM, root and AD-free. This means, that this is not 100% original and the Tab reject the online-Update.
That's the reason, that I was going also the way via "Back to stock" which is described in the attached pdf. After the Tab was finish to flash the stock-FW, the TAB stocks at the point with the Olympic rings. Here a RESET of all User-data (Factory-Reset) must be done and the Tab start without any error. Now I was able to received all online-Updates and the TAB was up-to-date (Stock-FW).
After time, the new CWM was published ... but this is a another story. First of all, the Tab should be flash the upgrade.zip, booting, and update by hishelf via WLAN
Wesie said:
you does not make the change with a normal Windows-Editor ( diff. CR&LF )
Click to expand...
Click to collapse
and do not use WinRar to save the changed zip, you can use 7zip for this.
In the case Wesie will allow you to use fastboot you can try this:
you can install the complete firmware.zip using fastboot "fastboot update xxx.zip"
or you can search for all the five .img files and flash them with fastboot "fastboot flash [partition] [imagefile.img]"
- recovery.img
- bootloader.img
- boot.img
- system.img
- flexrom.img (partition name is flex)
for a bootable tablet you only need bootloader, boot and system - also you can try some custom ROMs
Don't know what's happen in the meantime : no response form chipzter at all . Maybe the Tab is working, maybe not
@Paulinche
The tip to flash the complete upgrade.zip via fastboot is nice :good:
I haven't know this one: THX!
Moscow Desire said:
Remember that the sequence to boot to stock recovery, is different in ICS than the sequence steps for JB. I guess this changed with the release of JB. Honestly, can't remember how to boot to recovery on ICS (I always use adb, but that won't work for you.) At least on the 700 it did.
Click to expand...
Click to collapse
The key sequence to enter recovery that worked before (although the recovery process itself did not) was to hold down the two-dots button while powering on and releasing the power button when it vibrates. I assume that it's the boot loader that reacts to the key presses and since I still have the ICS boot loader, the recovery key sequence should be the same. Besides, there's no second vibration if I keep pressing the two-dots button.
Moscow Desire said:
If the recovery.img flashed successfully, then there's no reason why you shouldn't be able to boot to it. Don't know the sequence for the ICS 510, but on the A500, it was vol- and pwr.
Click to expand...
Click to collapse
Yeah, that's what I can't figure out. Why doesn't it boot into recovery, no matter what kind of recovery.img I flash.
Moscow Desire said:
Another idea, is to see if anybody has a boot.img, system.img and flexrom.img for ICS. Then you can simply fastboot it.
Click to expand...
Click to collapse
If any one has those three .img files, I'd appreciate it a lot if I could get copies of them and see if it would help revive my tablet. All A510 owners I know have all upgraded to JB. :crying:
Moscow Desire said:
As with the bootloader, it's correct. You have to use NVFlash to flash the .bin. You can however, flash a bootloader.blob via CWM though. I helped a person last month get his tab straight using that method.
Click to expand...
Click to collapse
That was my original plan. If I could get the CWM recovery working, I'd stand a chance of restoring the device using an official update file.
---------- Post added at 11:30 PM ---------- Previous post was at 11:22 PM ----------
Wesie said:
Does you've follow the instruction which Acer attached?
If the original update.zip failed in the beginning, you must modify the first line in the update.zip [add a # in front; thats all]
META-INF\com\google\android\updater-script
Click to expand...
Click to collapse
I was pretty sure that would not work since I no longer get the "Booting recovery kernel image" image when I try to enter recovery mode. And since recovery mode won't start, it will not even look for the update.zip file. I tried it just to make sure, but it didn't work. I'm on a mac so I used the built in zip function.
---------- Post added at 11:38 PM ---------- Previous post was at 11:30 PM ----------
Paulinche said:
you can install the complete firmware.zip using fastboot "fastboot update xxx.zip"
Click to expand...
Click to collapse
I tried to use "fastboot update" but it seems that the content of the zip file is different from the zip file used for SD card updates because fastboot outputs the following error messages:
./fastboot update ~/Downloads/iconia/OS_Acer_RV28RC01.EMEA.CUS1_A40I_A/update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Does anyone know where I might find a firmware.zip file for A510 that works with fastboot? That would be awesome!
---------- Post added at 11:42 PM ---------- Previous post was at 11:38 PM ----------
Wesie said:
Don't know what's happen in the meantime : no response form chipzter at all . Maybe the Tab is working, maybe not
Click to expand...
Click to collapse
Sorry for not staying in touch. But I promise to let you guys know if I get my tablet working! (Which it isn't in case there was any doubt )
OK,
I believe, you've the bootloader from ISC on the TAB. (please write the No. which is in the Display a ahort time during boot)
If you want to flash a version - and you didin't know which one you have had - I think, this one is not a bad one: OS_Acer_RV28.RC02.WW.GEN1_A40I_A
Extract the update.zip from the archiv and copy this one on root of the external-SD card.
Normally you can start the flash procedure with:
Hold the Volume ** (don't release)
press and Hold the POWER (don't release)
TILL you can read "Recovery in the upper left corner
or following the description in the pdf:
Hold the volume ** (don't release)
Hold Power (don't release)
Once "Power"key white LED lights, released the POWER BUT still hold the Volume**
If you can read "Erasing cache .... " released the Volume**
than the TAB should start the flashing. If the update failed (about the version-check), than we can modify the update.zip.
Please confirm, that the Recovery process is started ...and also was is happen, does the Tab start to flash, interrrupt after a few second ... does not start to flash ...
All A510 owners I know have all upgraded to JB
Click to expand...
Click to collapse
so as written before:
I've a backup from my Tab - before i've upgrade to JB- from the DE-Version, but you can selected English as language, too - after CWM, root and install "ad-free". If you want, you can have a copy of this files.
Wesie said:
OK,
I believe, you've the bootloader from ISC on the TAB. (please write the No. which is in the Display a ahort time during boot)
If you want to flash a version - and you didin't know which one you have had - I think, this one is not a bad one: OS_Acer_RV28.RC02.WW.GEN1_A40I_A
Click to expand...
Click to collapse
The only thing displayed during boot is the following line:
Bootloader Version 0.04.04-ICS-MDRR (Unlock Mode)
Wesie said:
Hold the Volume ** (don't release)
press and Hold the POWER (don't release)
TILL you can read "Recovery in the upper left corner
or following the description in the pdf:
Hold the volume ** (don't release)
Hold Power (don't release)
Once "Power"key white LED lights, released the POWER BUT still hold the Volume**
If you can read "Erasing cache .... " released the Volume**
Click to expand...
Click to collapse
I've tried both methods several times but absolutely nothing happens. It still just says Bootloader Version 0.04.04-ICS-MDRR (Unlock Mode)
Wesie said:
so as written before:
I've a backup from my Tab - before i've upgrade to JB- from the DE-Version, but you can selected English as language, too - after CWM, root and install "ad-free". If you want, you can have a copy of this files.
Click to expand...
Click to collapse
I would really appreciate copies of those files! I know enough German to find my way around a computer. At least enough to switch the language to English!
Q&A for **TWRP** custom recovery for IDOL3 6045
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for **TWRP** custom recovery for IDOL3 6045. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
stuck on twrp bootloop
stuck on twrp boot loop. any suggestions? i followed instructions as posted, but when rebooted into twrp and tried to reboot system, i keep going back to twrp. thanks
Heyy
I have the same problem,, although i did a backup and then a deleted everything cause it was looping,,, how do i fix everything to the original condition,, i won't be doing this again,, my model is an i version.. Although mine is not booting into twrp ,, just the original..
Restoring my backup does not work
I tryed everything,, i know not to do this anymore I think it's broke forever.
If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...
Where is the system image?
neilownz said:
If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...
Click to expand...
Click to collapse
---------- Post added at 12:30 AM ---------- Previous post was at 12:20 AM ----------
im in tears (
I believe there's a link in the thread about ota updates after rooting.
http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
Click to expand...
Click to collapse
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...
TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...
Click to expand...
Click to collapse
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.
I can't even get into TWRP mode now it reboots too fast now..
maigre said:
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.
Click to expand...
Click to collapse
You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).
I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?
datkevjames said:
I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?
Click to expand...
Click to collapse
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
maigre said:
You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).
Click to expand...
Click to collapse
If you can execute fastboot commands, your already in bootloader.
famewolf said:
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
If you can execute fastboot commands, your already in bootloader.
Click to expand...
Click to collapse
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.
twrp bootloop
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.
datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.
Click to expand...
Click to collapse
There are no install-script and install-binary example files to use to build a signed update.zip because there are no rom's available....maybe someone could build something using the spanish rom just posted but I don't read spanish and they seem to have built it for a 6045Y which isn't gonna help 6045i or 6045K users. If you were running twrp it wouldn't be an issue as twrp allows adb access....stock recovery doesn't..it also doesn't support rebooting to bootloader....if your bootup was "freezing" as a normal build.prop issue would then you should STILL be able to do an "adb reboot bootloader" or an "adb shell" and look around.
datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
.
Click to expand...
Click to collapse
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
---------- Post added at 10:58 AM ---------- Previous post was at 10:50 AM ----------
faresbreech said:
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.
Click to expand...
Click to collapse
if you have a problem then:
1- you have to tell what did you do before it happen.
anyway if you can go to TWRP, you can download system Image backup from @famewolf thread HERE, copy it to your sd card and then proceed with restore menu from TWRP. And just check the "system" .
First I rooted phone, then verified through root checker that I was truly rooted. After that I proceeded to flash twrp. Once twrp was flashed, I went to recovery to make a full backup. There I first chose read only and then backed up, but realized that I was limited on performing different actions so I reflashed twrp and this time I chose for twrp to fully work and again preformed another backup. It was when I rebooted system after the second backup when I started looping back to twrp.
I was wondering if maybe there is a terminal command I can execute through twrp to fix this like the LG G2 has. I had a problem like this before on my G2 but after executing the terminal command it would get fixed. Thanks
Sent from my Z987 using XDA Free mobile app
DallasCZ said:
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
Click to expand...
Click to collapse
I tried spamming 'adb reboot-bootloader' as fast as possible, but apparently I didn't authorize my computer. ADB gives me this: error: device unauthorized. Please check the confirmation dialog on your device. ffs. Now what? I do appreciate all help. I am savvy enough to try to solve this on my own but any helpful advice would be awesome.
please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you
Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help
Why do you need to downgrade? Messing with Bootloaders can destroy your phone.
even i want to downgrade... I cant flash custom recovery on 41.1A
poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.
Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...
@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.
kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).
I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk
I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.
How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!
Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?
_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.
_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.
i had the problem, when the cell, automatic restarted and it stuck on this screens, but it never came back, i already tried flashing the cellphone, and i already tried adding a custom bootloader, but no luck, it gave me the information that it mismatch, and attempts to enter the bootloader, without luck, i also already tried to only boot with fastboot, and no luck, it stucks on the twrp or m screen or shows different issues like screen fading or rumbling without reason, attempted to enter the recovery and only got to normal recovery from android, attempted to sideload the zip, and got a verification error, and it fails, again, i cant install a custom recovery, it always fails, and i dont know what to do... i really need help, any suggestion?? i already searched and didnt found any tools, flasher tool v.2 not found, and other tools are not able to help as well, help!!
edit, forgot to add, its an moto g. 2013 , xt1032 ANDROID LOLLIPOP
x-fighter said:
i had the problem, when the cell, automatic restarted and it stuck on this screens, but it never came back, i already tried flashing the cellphone, and i already tried adding a custom bootloader, but no luck, it gave me the information that it mismatch, and attempts to enter the bootloader, without luck, i also already tried to only boot with fastboot, and no luck, it stucks on the twrp or m screen or shows different issues like screen fading or rumbling without reason, attempted to enter the recovery and only got to normal recovery from android, attempted to sideload the zip, and got a verification error, and it fails, again, i cant install a custom recovery, it always fails, and i dont know what to do... i really need help, any suggestion?? i already searched and didnt found any tools, flasher tool v.2 not found, and other tools are not able to help as well, help!!
edit, forgot to add, its an moto g. 2013 , xt1032 ANDROID LOLLIPOP
Click to expand...
Click to collapse
which bootloader?
locked?
which firmware?
flashed how?
Sent from my PH-1 using XDA Labs
sd_shadow said:
which bootloader?
locked?
which firmware?
flashed how?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
x-fighter said:
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
Click to expand...
Click to collapse
https://m.imgur.com/nSFMea9
http://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg
Sent from my PH-1 using XDA Labs
---------- Post added at 01:48 PM ---------- Previous post was at 01:47 PM ----------
neither one of those says what files you are trying to flash
Sent from my PH-1 using XDA Labs
attached
Sent from my PH-1 using XDA Labs
x-fighter said:
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
Click to expand...
Click to collapse
From the picture you uploaded, says that your bootloader is locked, so that is why you can't flash any custom recovery. First you need to unlock your bootloader first but BACKUP FIRST, cause it will erase your internal storage when you unlock your bootloader. After unlocked, then you can flash custom recovery. Hope that helps.
Edit: but if your bootloader is really already unlocked, than try this, flashed twrp, then power down your phone by pressing the power button, then boot to twrp by press power button + volume down buttom. Don't reboot to twrp using the option im bootloader mode or using adb.
tepar said:
From the picture you uploaded, says that your bootloader is locked, so that is why you can't flash any custom recovery. First you need to unlock your bootloader first but BACKUP FIRST, cause it will erase your internal storage when you unlock your bootloader. After unlocked, then you can flash custom recovery. Hope that helps.
Edit: but if your bootloader is really already unlocked, than try this, flashed twrp, then power down your phone by pressing the power button, then boot to twrp by press power button + volume down buttom. Don't reboot to twrp using the option im bootloader mode or using adb.
Click to expand...
Click to collapse
i will upload a more reccent one, where i already unlocked it, but i will try whaat you edited, thank you!! let me try and post results
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
aktiv8d said:
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Whoareyou said:
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Click to expand...
Click to collapse
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
aktiv8d said:
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
Click to expand...
Click to collapse
They're only sent out by OnePlus when someone needs to restore their phone due to malfunction, not released on any regular basis, but this one has been around for a while.
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
---------- Post added at 03:51 AM ---------- Previous post was at 03:37 AM ----------
mimat1 said:
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
Click to expand...
Click to collapse
UPDATE: I flashed it by starting the MSMDownloader while in EDL mode. Much thanks for this method and fix. My phone thanks you for revival!
Narwhal73 said:
Ok so for future people who run into the same problem and are clueless like me! The RAR file contains the system image and an MSM Tool. Unrar it, open the tool, put your phone in EDL mode, make sure the tool recognizes the device, then click "start".
Cheers!
Click to expand...
Click to collapse
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
---------- Post added at 07:36 PM ---------- Previous post was at 07:22 PM ----------
Narwhal73 said:
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
Click to expand...
Click to collapse
Ok, I was really spooked by the Android 9 ROM saying my device was SIM locked when I bought it unlocked.
On point with answering my own questions: applying the OTA update now shows that my phone is unlocked (as it should be!) under Settings > System updates > UICC unlock.
My phone always reboots to fastboot. I've opened MSM tool and my phone doesn't appear there. It does appear using fastboot devices command on CMD though. How can I flash this? Restart recovery or restart bootloader does nothing, always back to fastboot.