Database Info

TF700 bootlooping on twrp splash screen

Hi
After trying to install crombi on tf700 using twrp 2.7 something went wrong and now tablette is bootlooping on twrp screen.
Cpnnected the tablette to laptop and nothing appears in the M'y Computer Windows.
Checked on device manager and found 'transformer' writen there with yellow exclamation Mark.
Tried to update driver with nô success.
Any help Will be greatly appreciated
Thanks

We need more information.
What did you come from?
What's your bootloader and rom versions?
Did you do a full wipe?
Describe in detail the procedure you followed.

berndblb said:
We need more information.
What did you come from?
What's your bootloader and rom versions?
Did you do a full wipe?
Describe in detail the procedure you followed.
Click to expand...
Click to collapse
Hi and thanks for the reply.
The tablet was on the latest Cromi-x and bootloader.
Did a full wipe and begun installing crombi
The tablet was stuck a long time on formatting so I had to regoot
After the reboot it was unable to moiunt E,
Tried to do another full wipe and now the tablet is just bootlooping on the TWRP splashscreen.
Any suggestion?

Formatting with TWRP 2.7 can take 90 minutes. You should not have interrupted it.
Can you get into fastboot?
Or alternatively you can try to get an adb connection when the tablet is looping.

berndblb said:
Formatting with TWRP 2.7 can take 90 minutes. You should not have interrupted it.
Can you get into fastboot?
Or alternatively you can try to get an adb connection when the tablet is looping.
Click to expand...
Click to collapse
Thanks for the answer so just connect the tablet, open cmd and do adb devices ?
Will try it in 30 min as I am not home
Tried the adb devices on a command windows in the platform-tools directory and nothing comes after hitting enter
Anything else to try?

What about fastboot? Boot with Volume Down and Power. Then try
'fastboot devices'
Sent from my DROID4 using Tapatalk

allotesting said:
Thanks for the answer so just connect the tablet, open cmd and do adb devices ?
Will try it in 30 min as I am not home
Tried the adb devices on a command windows in the platform-tools directory and nothing comes after hitting enter
Anything else to try?
Click to expand...
Click to collapse
Nothing? something must come up. What does it say? Command not found? No devices found?

sbdags said:
Nothing? something must come up. What does it say? Command not found? No devices found?
Click to expand...
Click to collapse
Hi
When I try the fastboot devices command it comes back to the invite with nothing written
When I try the adb devices nothing after list of devices attached
And the tablet keeps on bootlooping on the teamwin splash screen
And as already stated in device manager I find the mention transformer with yellow mark

Hi
Something new after I tried to update driver
Tried the fastboot command and it found something
It gives me s bunch of numbers and letters and recovery at the end
Is it good doctor?

Tried to install TWRP using fastboot -I 0x0B05 flsh recovery TWRP.blob and it sots there with the message <waiting for device> and tablet is still bootlooping:crying:

allotesting said:
Tried to install TWRP using fastboot -I 0x0B05 flsh recovery TWRP.blob and it sots there with the message <waiting for device> and tablet is still bootlooping:crying:
Click to expand...
Click to collapse
Are you in the boot loader when you issue that command?

By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks

allotesting said:
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
Click to expand...
Click to collapse
Yes that is normal. What happens when you flash twrp with fasboot. What does it report back?

allotesting said:
By the way the bunch of numbers and letters are 0123456789ABCDEF and I have ASUS android ADB Interface under ASUS Android Devices in device manager
I don't know if this helps
Thanks
Click to expand...
Click to collapse
Ok, I think we need to clear up some things:
If the tablet is bootlooping it cannot be in the bootloader and fastboot mode (you are in the bootloader menu when you see the 3 icons: RCK, Android, Wipe Data). But if you see the adb interface in Device Manager while it is looping you should have an adb connection and
Code:
adb devices
should return a similar but different string of numbers and letters.
Code:
adb reboot-bootloader
should boot you into the bootloader which is also fastboot mode.
In fastboot you should be able to flash TWRP with the command you posted, minus the typos naturally.
It has to be
Code:
fastboot devices
and it has to return the string of letters and numbers, then:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
Try that and report back

Hi there, I have the exact same problem. I tried searching all over about the time for a full wipe and couldn't find anything. So after about an hour I hard powered down. Of course, when I started researching the recovery look, I found the info (roughly 90-120 minutes). Here is what I have done to try to rectify, perhaps you can help. I booted into the bootloader and ran the following commands:
C:\>fastboot devices
015d2bbcc413ea10 fastboot
C:\>cd adb
C:\adb>dir
Volume in drive C has no label.
Volume Serial Number is 48F6-D102
Directory of C:\adb
04/29/2014 11:49 PM <DIR> .
04/29/2014 11:49 PM <DIR> ..
04/25/2014 06:59 AM 819,200 adb.exe
04/25/2014 06:59 AM 96,256 AdbWinApi.dll
04/25/2014 06:59 AM 60,928 AdbWinUsbApi.dll
04/25/2014 06:59 AM 160,256 fastboot.exe
04/29/2014 11:49 PM 6,443,112 openrecovery-twrp-2.7.0.0-tf700t.blob
5 File(s) 7,579,752 bytes
2 Dir(s) 672,096,153,600 bytes free
C:\adb>ren openrecovery-twrp-2.7.0.0-tf700t.blob twrp.blob
C:\adb>dir
Volume in drive C has no label.
Volume Serial Number is 48F6-D102
Directory of C:\adb
04/29/2014 11:50 PM <DIR> .
04/29/2014 11:50 PM <DIR> ..
04/25/2014 06:59 AM 819,200 adb.exe
04/25/2014 06:59 AM 96,256 AdbWinApi.dll
04/25/2014 06:59 AM 60,928 AdbWinUsbApi.dll
04/25/2014 06:59 AM 160,256 fastboot.exe
04/29/2014 11:49 PM 6,443,112 twrp.blob
5 File(s) 7,579,752 bytes
2 Dir(s) 672,096,088,064 bytes free
C:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6292 KB)...
OKAY [ 2.459s]
writing 'recovery'...
OKAY [ 7.564s]
finished. total time: 10.023s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.022s
Click to expand...
Click to collapse
When I reboot into the bootloader and click RCK I get the TEAMWIN logo (blue screen). About every 2-3 seconds the screen goes black and the TEAMWIN logo shows again.
Thoughts?
---------- Post added 30th April 2014 at 12:16 AM ---------- Previous post was 29th April 2014 at 11:56 PM ----------
I decided to play around a little more to see what I could do. I pushed TWRP v2.6.3.2 to the device replacing v2.7. Finally I was able to get into TWRP. However, now I am stuck. TWRP asks me for a password that was never set (I don't have one). I hit cancel and the main menu and I show as having -1mb of internal storage.
If I try any commands, I am told that there aren't permissions to access the partitions. I feel like I am getting closer.
If I tell TWRP to FORMAT DATA in the WIPE menu, recovery restarts and asks me for my password again.
Thoughts?

BigKenW said:
Hi there, I have the exact same problem. I tried searching all over about the time for a full wipe and couldn't find anything. So after about an hour I hard powered down. Of course, when I started researching the recovery look, I found the info (roughly 90-120 minutes). Here is what I have done to try to rectify, perhaps you can help. I booted into the bootloader and ran the following commands:
When I reboot into the bootloader and click RCK I get the TEAMWIN logo (blue screen). About every 2-3 seconds the screen goes black and the TEAMWIN logo shows again.
Thoughts?
---------- Post added 30th April 2014 at 12:16 AM ---------- Previous post was 29th April 2014 at 11:56 PM ----------
I decided to play around a little more to see what I could do. I pushed TWRP v2.6.3.2 to the device replacing v2.7. Finally I was able to get into TWRP. However, now I am stuck. TWRP asks me for a password that was never set (I don't have one). I hit cancel and the main menu and I show as having -1mb of internal storage.
If I try any commands, I am told that there aren't permissions to access the partitions. I feel like I am getting closer.
If I tell TWRP to FORMAT DATA in the WIPE menu, recovery restarts and asks me for my password again.
Thoughts?
Click to expand...
Click to collapse
It seems as if TWRP thinks your data partition is encrypted.
Boot into recovery, make sure you have an adb connection with
Code:
adb devices
if that returns a string of letters and numbers try
Code:
adb killall recovery
This should get you back to recovery and then try to format data again.
Good luck

berndblb said:
It seems as if TWRP thinks your data partition is encrypted.
Boot into recovery, make sure you have an adb connection with
Code:
adb devices
if that returns a string of letters and numbers try
Code:
adb killall recovery
This should get you back to recovery and then try to format data again.
Good luck
Click to expand...
Click to collapse
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
Click to expand...
Click to collapse
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
---------- Post added at 01:18 AM ---------- Previous post was at 12:55 AM ----------
BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
Click to expand...
Click to collapse
Alright, nothing I can do will fix this thing. The internal drive shows 0mb. I even tried installing CWM and I can't mount any partitions. I would like to return to full stock. I can't seem to find anything like an RUU or other tool to do this. Can someone please direct me to the best thread to do so?
After I am back stock I will unlock the bootloader again.

I will follow all the commands when I will be back from work. It's 3:30 here in Montreal thanks guys

BigKenW said:
Thanks for the advice. I actually reflashed to 5.7 and the password request is no longer there. That said, the device cannot mount anything inside. When I try ADB devices I am returned with nothing. That seems odd to me if fastboot commands work.
I searched around and a lot of people returned to full stock. I could also try the WIPE DATA option in the bootloader. But everything I have read is that is VERY bad. If I did that, even if I had to repush TWRP, would that be bad?
---------- Post added at 12:55 AM ---------- Previous post was at 12:33 AM ----------
OK, I was able to get ADB going. The computer I was using didn't have the driver setup. That is fixed. The killall recovery command doesn't seem to work.
---------- Post added at 01:18 AM ---------- Previous post was at 12:55 AM ----------
Alright, nothing I can do will fix this thing. The internal drive shows 0mb. I even tried installing CWM and I can't mount any partitions. I would like to return to full stock. I can't seem to find anything like an RUU or other tool to do this. Can someone please direct me to the best thread to do so?
After I am back stock I will unlock the bootloader again.
Click to expand...
Click to collapse
To return to stock just download the Asus firmware, unzip it once and flash the resulting zip in recovery.
Your bootloader will stay unlocked. You just have to flash a custom recovery again, reboot and then flash the rom.

allotesting said:
I will follow all the commands when I will be back from work. It's 3:30 here in Montreal thanks guys
Click to expand...
Click to collapse
Hi all
Back from work but all the commands were uselee
In device manager I have ASUS android ADB interface after updating manually the 'transformer' that I had with the yellow matk
When trying adb devices it comes with 0123456789ABCDEF all the hexadecimal digits so seems to me that the machine does not recognize the tablet itself
When trying fastboot devices and hit enter it comes back to the >invite
When trying adb reboot-bootloader it just sits there with even no >invite
Forgot to mention that the word recovery comes after the 0123456789ABCDEF on the adb devices
Anything else to try? Thanks

[Q&A] **TWRP** custom recovery for IDOL3 6045

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.

[GUIDE] De-branding Your 3 Handset

Hi guys here is a we guide on how to successfully de-brand you 3 device in order to get OTA updates working and installing correctly.
1. You will need adb and fastboot installed on your system in order to do the process.
For windows systems you can refer to this thread on installing adb and fastboot
https://forum.xda-developers.com/showthread.php?t=2588979
For linux based systems you can install both using this command
For Debain Based i.e Ubuntu, LinuxMint etc...
Code:
sudo apt update
sudo apt install android-tools-adb android-tools-fastboot
For Centos or Fedora you can use this command:
Code:
sudo yum install android-tools
2. Download the required Global Razer factory image
cheryl-global-851.zip
Mirror:
https://mega.nz/#!LFRhSR5Y!qAiyf3q3gmSt5bFtVd528qWAWmempSJLg3nyTjHxkw4
3. Unlocking the bootloader
WARNING: THIS PART FORMATS YOUR USER DATA SO MAKE A BACKUP OF YOUR INTERNAL STORAGE BEFORE PROCEEDING.
After you have everything installed and the image downloaded you will need to unlock two parts of the bootloader snippets from Razers site:
Unlocking the Bootloader
Enable OEM Unlocking
If necessary, enable OEM unlocking on the Razer Phone:
On Android 7.x, go to Settings > About phone > tap Build number seven (7) times.
Tap the back button once you see the “You are now a developer” message appear.
Tap Developer options, tap toggle OEM unlocking to enable.
Enter Download Mode
Start the Phone in Download Mode with one of the following methods:
Using the adb tool: With the Phone powered on, execute: adb reboot bootloader
Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
Unlock the Bootloader
Run this command: fastboot flashing unlock
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot.
Unlock the Bootloader Critical Partitions
Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
The unlock can be performed with this command: fastboot flashing unlock_critical
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot.
4. Flashing the image.
Download the appropriate system image for the Razer Phone from here, then unzip it to a safe directory.
Connect your Razer Phone to your computer over USB.
Start the Phone in Download Mode with one of the following methods:
Using the adb tool: With the Phone powered on, execute: adb reboot bootloader
Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
If necessary, unlock the Phone’s bootloader. See Unlocking the Bootloader and Unlocking the Bootloader Critical Partitions for instructions.
Open a terminal on your computer and navigate to the unzipped system image directory.
Execute the flash_all.sh script if on linux or on windows run flash_all.bat. This script installs the necessary bootloader, baseband firmware(s), and operating system for your Razer Phone.
Once the script finishes, your Phone will reboot.
5. Covering up what you have done i.e removing the error during boot.
Locking the Bootloader
Locking the bootloader is recommended for security reasons. Some applications will not work with an unlocked bootloader.
Start the Phone in Download Mode with one of the following methods:
Using the adb tool: With the Phone powered on, execute: adb reboot bootloader Enter Download Mode:
Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
Lock the critical partitions of the Bootloader first by running this command: fastboot flashing lock_critical
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot.
Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
Locking the remainder of the bootloader can be performed with this command: fastboot flashing lock
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot.
Once you have done all that your phone will be de-branded
thanks to @Xplicit1992 for tipping me off that otas work after flashing the MR1 global image

OTA update found but fail to update. (Tested from MR2)

LttHckr said:
OTA update found but fail to update.
Click to expand...
Click to collapse
Did you flash the correct global image posted above cause I know it works as I tested before I made the thread and the OTA downloads and installed just fine for me

eoghan2t7 said:
Did you flash the correct global image posted above cause I know it works as I tested before I made the thread and the OTA downloads and installed just fine for me
Click to expand...
Click to collapse
I've tested from MR2, OK I will try again on MR1.

LttHckr said:
I've tested from MR2, OK I will try again on MR1.
Click to expand...
Click to collapse
@eoghan2t7 I try to flash from MR1 and OTA update to MR3 success thank you.

I bought the phone on contract with 3. If I do this will it break VoLTE ("4G Super Voice")?

Hey guys, when trying to push the file over, nothing happens. If i dont do the fastboot -i 0x1532 it gets stuck on waiting for device. i dont know what to do now
?
PS C:\Users\usera\Downloads\cheryl-global-851> fastboot -i 0x1532 flash partition:0 gpt_both0.bin
target reported max download size of 536870912 bytes
sending 'partition:0' (44 KB)...
OKAY [ 0.003s]
writing 'partition:0'...
OKAY [ 0.093s]
finished. total time: 0.097s
PS C:\Users\usera\Downloads\cheryl-global-851>
---------- Post added at 12:21 PM ---------- Previous post was at 12:08 PM ----------
C:\Users\usera\Downloads\cheryl-global-851>set fastboot_cmd=fastboot
C:\Users\usera\Downloads\cheryl-global-851>fastboot flash partition:0 gpt_both0.bin
< waiting for device >
thats what I get, and it doesnt move from there

comady25 said:
I bought the phone on contract with 3. If I do this will it break VoLTE ("4G Super Voice")?
Click to expand...
Click to collapse
Honestly don't know how to test volte that.
userade123 said:
Hey guys, when trying to push the file over, nothing happens. If i dont do the fastboot -i 0x1532 it gets stuck on waiting for device. i dont know what to do now
?
PS C:\Users\usera\Downloads\cheryl-global-851> fastboot -i 0x1532 flash partition:0 gpt_both0.bin
target reported max download size of 536870912 bytes
sending 'partition:0' (44 KB)...
OKAY [ 0.003s]
writing 'partition:0'...
OKAY [ 0.093s]
finished. total time: 0.097s
PS C:\Users\usera\Downloads\cheryl-global-851>
---------- Post added at 12:21 PM ---------- Previous post was at 12:08 PM ----------
C:\Users\usera\Downloads\cheryl-global-851>set fastboot_cmd=fastboot
C:\Users\usera\Downloads\cheryl-global-851>fastboot flash partition:0 gpt_both0.bin
< waiting for device >
thats what I get, and it doesnt move from there
Click to expand...
Click to collapse
For best results I recommend using a Ubuntu live disk when flashing the images or make a small dual boot on your PC dedicated to flashing your phone.

Hey another guy from Belfast
Nice guide man I'm glad people can finally get rid of the three ROM

Roxas598 said:
Hey another guy from Belfast
Nice guide man I'm glad people can finally get rid of the three ROM
Click to expand...
Click to collapse
Tell me about it now updates should be instantly available to us Belfast folk ?

eoghan2t7 said:
Tell me about it now updates should be instantly available to us Belfast folk
Click to expand...
Click to collapse
Just got my Razer Phone (again lol) And debranded successfully Thanks man!

Thankyou very much for the guide it worked a treat.
I had to slightly amend your script as I was also having the fasbtoot only recognising "fastboot -i 0x1532"
But only had to change one part of your it so the rest of the script would use "fasbtoot" as fastboot -i 0x1532
Worked as it should.
But thanks again. Anyone else having similar issues I can confirm this worked with my 3 branded device.
Sent from my Phone using Tapatalk

I reboot to download mode and issue the fast boot command phone just sits at download mode and cmd line has waiting for device ??
---------- Post added at 08:23 AM ---------- Previous post was at 08:20 AM ----------
I reboot to download command from cmd window download mode appears at the top left of the screen I issue the unlock command it just says waiting on the device I have OEM unlock selected in dev options have USB debugging enabled and accepted to allow reboot and commands when I issue unlock commands it sits at waiting on device

can you give instructions on how to use Ubuntu live disk when flashing the images? thank you!

nexy33 said:
I reboot to download mode and issue the fast boot command phone just sits at download mode and cmd line has waiting for device ??
---------- Post added at 08:23 AM ---------- Previous post was at 08:20 AM ----------
I reboot to download command from cmd window download mode appears at the top left of the screen I issue the unlock command it just says waiting on the device I have OEM unlock selected in dev options have USB debugging enabled and accepted to allow reboot and commands when I issue unlock commands it sits at waiting on device
Click to expand...
Click to collapse
While your phone is in download mode check the device manager on the PC see if it detects the device properly or has a warning triangle beside it. If it does then your PC isn't detecting the hardware properly and you'll need to download android ADB drivers.

Roxas598 said:
While your phone is in download mode check the device manager on the PC see if it detects the device properly or has a warning triangle beside it. If it does then your PC isn't detecting the hardware properly and you'll need to download android ADB drivers.
Click to expand...
Click to collapse
YIP has a warning triangle on android device

nexy33 said:
YIP has a warning triangle on android device
Click to expand...
Click to collapse
yep that's your issue then. right click on it and select "update drivers" then select the option that reads something like install from your computer then to chose a driver. if you can't see "Android ADB" then you'll need to install these https://developer.android.com/studio/run/win-usb.html then do what I said there.
Should get your computer talking to the phone in download mode

Roxas598 said:
yep that's your issue then. right click on it and select "update drivers" then select the option that reads something like install from your computer then to chose a driver. if you can't see "Android ADB" then you'll need to install these https://developer.android.com/studio/run/win-usb.html then do what I said there.
Should get your computer talking to the phone in download mode
Click to expand...
Click to collapse
tried all 3 drivers that cpomes in that still wont talk to pc in dl mode im on rs3

nexy33 said:
tried all 3 drivers that cpomes in that still wont talk to pc in dl mode im on rs3
Click to expand...
Click to collapse
Try installing wondershare mobilego on your pc, it get rid the missing drivers of mine after installing it.. i dont know why? might as well as yours

nexy33 said:
tried all 3 drivers that cpomes in that still wont talk to pc in dl mode im on rs3
Click to expand...
Click to collapse
Tried installing the "Android ADB" Driver in device manager? cause that should be the only thing stopping you :S so odd.

Micromax Canvas Infinity HS2 twrp and Root Magisk(finnaly root)

First read full steps iam not pro developer just share my experience(if step or missed just say)
Step 1. Download twrp Recovery for Your Device (HS2)From
Step 2. Download adb install.zip and extract From above adb and Fastboot driver Installer
Step 3. Now Install adb and fastboot Driver on Your pc, path(C:\Program Files\Minimal ADB and Fastboot or C:\Program Files (x86)\Minimal ADB and Fastboot)
Step 4. Go to Setting>about Phone>type 7 time Build number > Back>Developer Option and Enable Device Debugging And Oem Unlock
Step 5.Open the command on your PC. To open a command window in the current directory in Windows, press shift + Right Click anywhere on Windows explorer connect device into pc open CMD Here and type command :good:
Then follow Bellow Instructions be Remember Bootloader Must Unlock(open cmd " fastboot oem unlock-go" without qoutes)
Step 6. Unlock bootloader using below Code try first if fail then unlock using second Code
fastboot oem unlock-go
or
fastboot flashing unlock
And one think unlock bootloader if loss data and stoarge:silly:
Step7. Rename twrp into recovery.img and put in adb Folder
Step8.(cmd) fastboot boot recovery recovery.img (dont flash just boot)
Step9. Recovery is Now boot and copy magisk on stoarge
Download Magisk latest yours choice(but i prefer magisk 15.1). copy to Device storage [internatl/ external].
In the twrp Go to backup tab and Create a nadroid backup. Don’t forgot to include NVRAM or imei aka ESF in case any porblem or bootloop
Go to Install tab and Locate Download magisk and confirm Install, wait For Success Done.
[installed] make a System Reboot By this Command
fastboot reboot (if new member search how to recovery boot on android search youtube )
first boot may time pls just wait if sucess press thanks button

Error cannot load recovery.img
Plzzzz help

Hem97 said:
Error cannot load recovery.img
Plzzzz help
Click to expand...
Click to collapse
Screen shot

Hem97 said:
Error cannot load recovery.img
Plzzzz help
Click to expand...
Click to collapse
Unlock bootloder and say wat error

george.simbu said:
Unlock bootloder and say wat error
Click to expand...
Click to collapse
Yes i unlock bootloader...using cmd..
All okay but when i try 'fastboot boot recovery twrp.img'
Then 'permisen denied' shows
I am using xda app ..i dont know why says bad network cant upload screenshots

Hem97 said:
Yes i unlock bootloader...using cmd..
All okay but when i try 'fastboot boot recovery twrp.img'
Then 'permisen denied' shows
I am using xda app ..i dont know why says bad network cant upload screenshots
Click to expand...
Click to collapse
Usb debugging check and start

Hem97 said:
Yes i unlock bootloader...using cmd..
All okay but when i try 'fastboot boot recovery twrp.img'
Then 'permisen denied' shows
I am using xda app ..i dont know why says bad network cant upload screenshots
Click to expand...
Click to collapse
U have dnt unlock bootloder pls check that cmd using at post 2nd cmd

george.simbu said:
U have dnt unlock bootloder pls check that cmd using at post 2nd cmd
Click to expand...
Click to collapse
Bootloder issue

Yes i got it.....?
Factory data reset and then i do this tutorial....and i successfully flashed twrp
---------- Post added at 08:16 PM ---------- Previous post was at 08:11 PM ----------
Please port miui 9 or lineage os 15 for micromax canvas infinity hs2

Make time buddy my previous mobile hs2 but iam use still now mi a1 lets wait

george.simbu said:
Step1. Download twrp Recovery for Your Device (HS2)From
Step 2. Download adb folder From above and Fastboot driver Installer From above
Step 3. Go to Setting>about Phone>type 7 time Build number > Back>Developer Option and Enable Device Debugging And Oem Unlock.
Step 4. then follow Bellow Instructions, BE Remember Bootloader Must Unlock(open cmd " fastboot oem unlock-go" without qoutes)
Step 5. Now Install Correct adb and fastboot Driver on Your pc, Go to adb folder connect device into pc open CMD Here and type command .
tep7. Unlock bootloader using below Code try first if fail then unlock using second Code
fastboot flashing unlock
or
fastboot oem unlock-go
Step8. Rename twrp into recovery.img and put in adb Folder, To flash twrp Type-
fastboot boot recovery recovery.img(dont flash just boot)
Step9. Recovery is Now boot
Root Micromax Canvas Infinity-
Download Magisk latest(but i prefer magisk 15.1). Save it to Device storage [internatl/ external].
In the twrp Go to backup tab and Create a nadroid backup. Don’t forgot to include NVRAM or imei aka ESF.
Go to Install tab and Locate Download magisk and confirm Install, wait For Success Done.
[installed] make a System Reboot By this Command
fastboot reboot
first boot may time pls just wait if sucess press thanks button
thanks you xda
Click to expand...
Click to collapse
Are you sure this is the right recovery for micromax hs2, cuz i flashed this on my device and now its on bootloop, please don't put misleading stuff on xda. And moderators i request please dont allow people to fool others by promoting misleading tech stuff

Sudhangshu said:
Are you sure this is the right recovery for micromax hs2, cuz i flashed this on my device and now its on bootloop, please don't put misleading stuff on xda. And moderators i request please dont allow people to fool others by promoting misleading tech stuff
Click to expand...
Click to collapse
This right recovery and one member also sucess I am not fool mind you words

george.simbu said:
This right recovery and one member also sucess I am not fool mind you words
Click to expand...
Click to collapse
IAM just boot on recovery don't falshed

george.simbu said:
Step1. Download twrp Recovery for Your Device (HS2)From
Step 2. Download adb folder From above and Fastboot driver Installer From above
Step 3. Go to Setting>about Phone>type 7 time Build number > Back>Developer Option and Enable Device Debugging And Oem Unlock.
Step 4. then follow Bellow Instructions, BE Remember Bootloader Must Unlock(open cmd " fastboot oem unlock-go" without qoutes)
Step 5. Now Install Correct adb and fastboot Driver on Your pc, Go to adb folder connect device into pc open CMD Here and type command .
tep7. Unlock bootloader using below Code try first if fail then unlock using second Code
fastboot flashing unlock
or
fastboot oem unlock-go
Step8. Rename twrp into recovery.img and put in adb Folder, To flash twrp Type-
fastboot boot recovery recovery.img(dont flash just boot)
Step9. Recovery is Now boot
Root Micromax Canvas Infinity-
Download Magisk latest(but i prefer magisk 15.1). Save it to Device storage [internatl/ external].
In the twrp Go to backup tab and Create a nadroid backup. Don’t forgot to include NVRAM or imei aka ESF.
Go to Install tab and Locate Download magisk and confirm Install, wait For Success Done.
[installed] make a System Reboot By this Command
fastboot reboot
first boot may time pls just wait if sucess press thanks button
thanks you xda
Click to expand...
Click to collapse
Hello george simbu, actually you missed out couple of steps in this flashing process, when i tried using boot with recovery nothing happens, but when i flashed twrp the mobile goes into bootloop.
So how did i solved it, after flashing twrp i run the boot command in adb i.e. Fastboot boot recovery recovery.img, and then i finally be able to get my device out of bootloop
---------- Post added at 06:27 PM ---------- Previous post was at 06:24 PM ----------
george.simbu said:
This right recovery and one member also sucess I am not fool mind you words
Click to expand...
Click to collapse
And youre not fool, but next time when you try and make a tutorial please try put most of the processes into it, it actually helps the new people whose trying the flashing first time. Even i had a hard time sorting things with adb and fastboot command. It would be much appreciated if i would've got all of those command in just one place rather than going over and searching all of the internet for those commands

Foxhoundalpha said:
Hello george simbu, actually you missed out couple of steps in this flashing process, when i tried using boot with recovery nothing happens, but when i flashed twrp the mobile goes into bootloop.
So how did i solved it, after flashing twrp i run the boot command in adb i.e. Fastboot boot recovery recovery.img, and then i finally be able to get my device out of bootloop
---------- Post added at 06:27 PM ---------- Previous post was at 06:24 PM ----------
And youre not fool, but next time when you try and make a tutorial please try put most of the processes into it, it actually helps the new people whose trying the flashing first time. Even i had a hard time sorting things with adb and fastboot command. It would be much appreciated if i would've got all of those command in just one place rather than going over and searching all of the internet for those commands
Click to expand...
Click to collapse
yes iam re edits step if worng say iam changed

Error this device Micromax hs2

Milkhu said:
Error this device Micromax hs2
Click to expand...
Click to collapse
Factory reset and try again must bootloader unlock

Okay, for all those who are getting errors whatsoever, here i would like to tell you that i followed these steps and flashed twrp and rooted my device with magisk.. as explained by author..
1) unlock bootloader ( make sure to enable developer options, check unlock oem option, check debug option, check unknown sources in security option)
Use "fastboot oem unlock-go" as it worked for me on my canvas infinity hs2.
2) now after your fone is resetted after unlocking, do the initial setup with setting up account etc and once you at home screen go to settings and once again enable developer options, check unlock oem option, check debug option, check unknown sources in security.
Then connect fone to pc, you'll get adb promt on fone screen, allow it and on pc cmd type "adb reboot bootloader"
Then volume up on fone.
And on pc cmd type
Fastboot flash recovery twrp.img
(Well the author told to use boot command instead of flash, but boot didn't work for me so i used fastboot flash recovery twrp.img
Once this is done type
Fastboot reboot
And as the fone is about to reboot, quickly press volume down for twrp to load. Then you can transfer magisk from pc while twrp is on screen. And install magisk provided in the link.
Reboot and you will see your fone rooted. Voila. Done.

George.simbu did u ported any roms like lineage/RR for micromax canvas infinity
---------- Post added at 07:26 PM ---------- Previous post was at 07:25 PM ----------
I am just a noob and dont want to try porting roms on my hs2 as im afraid i might mess up my phone doing so

Foxhoundalpha said:
George.simbu did u ported any roms like lineage/RR for micromax canvas infinity
---------- Post added at 07:26 PM ---------- Previous post was at 07:25 PM ----------
I am just a noob and dont want to try porting roms on my hs2 as im afraid i might mess up my phone doing so
Click to expand...
Click to collapse
No brother

Network locked after update? Here's how I fixed it.

make sure you take a backup becuase this will wipe the device!!!!
1. reboot device to fastboot mode
2. run the flashall.bat file in NMK24B folder. this will downgrade everything to android N.
3. let it do its thing, once finished reboot device.
4. go through setup process then re enable usb debugging and reboot back to fastboot mode.
5. run fastboot command : "fastboot flashing unlock_critical" it should return device already unlocked.
6. place the 2 modem files in where you have adb/fastboot installed.
7. run command: fastboot flash modemst1 modemst1.img
8. run command: fastboot flash modemst2 modemst2.img
9. after both are flashed reboot device back to OS and you should be unlocked now.
10. you can now take the most recent update via ota and still be unlokced.
https://drive.google.com/file/d/1vRTRFMQEgblI3luGy1pEJC_WgW8LQrua/view?usp=drivesdk

Does this work while the phone is on Pie?

Hypnosis4U2NV said:
Does this work while the phone is on Pie?
Click to expand...
Click to collapse
Yes it reverts it to Android 7

Got Sprint locked Essential phone, you saved my day! Was getting "invalid SIM card" message, apparently seller didn't unlock it at Sprint. Your method worked from first time. OTA updated back to Pie, July 2019 patch, relocked bootloader, still carrier unlocked!

alex.vinarskis said:
Got Sprint locked Essential phone, you saved my day! Was getting "invalid SIM card" message, apparently seller didn't unlock it at Sprint. Your method worked from first time. OTA updated back to Pie, July 2019 patch, relocked bootloader, still carrier unlocked!
Click to expand...
Click to collapse
Your welcome!

I did this and now the screen is unresponsive to touch

357MagColt said:
I did this and now the screen is unresponsive to touch
Click to expand...
Click to collapse
While in TWRP screen or the phone boots into Nougat or PIE or Q and then this? We need more info.

HueyT said:
While in TWRP screen or the phone boots into Nougat or PIE or Q and then this? We need more info.
Click to expand...
Click to collapse
I got it to work now when I flash the modem files they don't seem to unlock it still shows invalid sim

357MagColt said:
I got it to work now when I flash the modem files they don't seem to unlock it still shows invalid sim
Click to expand...
Click to collapse
Sometimes it takes 1 day for this to work

Thank you so much for these instructions.... :highfive:
It's been so long since I used adb, it took me 10 minutes to hunt everything down again.
I completed all the steps, a few questions.. (observations really)
It pulled all OTAs and is now Android 10.
The phone does seem to work (data and voice).
It's also displaying my Verizon number.
However under "About Phone", the SIM still displays as Sprint. :silly:
It does not bother me. Just wanted to bring it up in case it turns out to be a broader issue.

alex.vinarskis said:
Got Sprint locked Essential phone, you saved my day! Was getting "invalid SIM card" message, apparently seller didn't unlock it at Sprint. Your method worked from first time. OTA updated back to Pie, July 2019 patch, relocked bootloader, still carrier unlocked!
Click to expand...
Click to collapse
Is this supposed to unlock sprint version ?

eishra said:
Is this supposed to unlock sprint version ?
Click to expand...
Click to collapse
This amazing tool does exactly that. Even a Sprint Locked phone with the Nag screen can be fixed.
---------- Post added at 11:36 PM ---------- Previous post was at 11:31 PM ----------
enigma2446 said:
make sure you take a backup becuase this will wipe the device!!!!
1. reboot device to fastboot mode
2. run the flashall.bat file in NMK24B folder. this will downgrade everything to android N.
3. let it do its thing, once finished reboot device.
4. go through setup process then re enable usb debugging and reboot back to fastboot mode.
5. run fastboot command : "fastboot flashing unlock_critical" it should return device already unlocked.
6. place the 2 modem files in where you have adb/fastboot installed.
7. run command: fastboot flash modemst1 modemst1.img
8. run command: fatsboot flash modemst2 modemst2.img
9. after both are flashed reboot device back to OS and you should be unlocked now.
10. you can now take the most recent update via ota and still be unlokced.
Please correct the spelling in step 8. fastboot is wrong
Click to expand...
Click to collapse

No luck!
Tried 10 thousands times with no luck! still saying network is not available / insert SIM card!
Any help?
Thanks
n2locarz said:
This amazing tool does exactly that. Even a Sprint Locked phone with the Nag screen can be fixed.
---------- Post added at 11:36 PM ---------- Previous post was at 11:31 PM ----------
enigma2446 said:
make sure you take a backup becuase this will wipe the device!!!!
1. reboot device to fastboot mode
2. run the flashall.bat file in NMK24B folder. this will downgrade everything to android N.
3. let it do its thing, once finished reboot device.
4. go through setup process then re enable usb debugging and reboot back to fastboot mode.
5. run fastboot command : "fastboot flashing unlock_critical" it should return device already unlocked.
6. place the 2 modem files in where you have adb/fastboot installed.
7. run command: fastboot flash modemst1 modemst1.img
8. run command: fatsboot flash modemst2 modemst2.img
9. after both are flashed reboot device back to OS and you should be unlocked now.
10. you can now take the most recent update via ota and still be unlokced.
Please correct the spelling in step 8. fastboot is wrong
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Verizon change to AT&T
Hello will this work for a Samsung s9 plus?. I bought it from eBay, which was booting up to the Verizon carrier unlocked but after doing 8 system updates (13-20) it now boot with AT&T and it is now network locked, NO SIM CARD

Need Help Sprint Locked
Does this require device bootloader to be unlocked ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:12 PM ----------
I need help - i am getting "getting FAILED (remote: Flashing is not allowed in Lock State)" when i try to run the flashall.bat

andril said:
Does this require device bootloader to be unlocked ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:12 PM ----------
I need help - i am getting "getting FAILED (remote: Flashing is not allowed in Lock State)" when i try to run the flashall.bat
Click to expand...
Click to collapse
Here is a couple of posts that have outlined the process better:
https://forum.xda-developers.com/showpost.php?p=75994498&postcount=360
https://forum.xda-developers.com/showpost.php?p=75507693&postcount=221
However, I have to caution you: you will be altering critical partitions on your phone and if you don't understand what you are doing and just blindly follow the posts you can make a minor mistake and brick your phone.
If any of those phrases sounds unfamiliar to you then don't try this method or at least ask someone with more experience to help you:
Unlocking bootloader
Flashing factory image via fastboot
Backing up and restoring modemst partitions

my adb says waiting ''for any device''

enigma2446 said:
make sure you take a backup becuase this will wipe the device!!!!
1. reboot device to fastboot mode
2. run the flashall.bat file in NMK24B folder. this will downgrade everything to android N.
3. let it do its thing, once finished reboot device.
4. go through setup process then re enable usb debugging and reboot back to fastboot mode.
5. run fastboot command : "fastboot flashing unlock_critical" it should return device already unlocked.
6. place the 2 modem files in where you have adb/fastboot installed.
7. run command: fastboot flash modemst1 modemst1.img
8. run command: fastboot flash modemst2 modemst2.img
9. after both are flashed reboot device back to OS and you should be unlocked now.
10. you can now take the most recent update via ota and still be unlokced.
https://drive.google.com/file/d/1vRTRFMQEgblI3luGy1pEJC_WgW8LQrua/view?usp=drivesdk
Click to expand...
Click to collapse
Dear, I wanted to thank you for your contribution and I wanted to know if you could help me with your knowledge to do a procedure similar to the PH-1. but to an LG G8 ThinQ