Related
Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
2/024/2012 01:24:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
12/024/2012 01:24:19 - INFO - Device connected with USB debugging on
12/024/2012 01:24:19 - INFO - Connected device : LT18
12/024/2012 01:24:19 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
12/024/2012 01:24:19 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
12/024/2012 01:24:41 - INFO - Root Access Allowed
12/025/2012 01:25:24 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
12/025/2012 01:25:24 - INFO - Device Status: ADB mode
12/025/2012 01:25:27 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
12/025/2012 01:25:28 - INFO - Device will soon enter fastboot mode
12/025/2012 01:25:29 - INFO - Device disconnected
12/025/2012 01:25:30 - INFO - Device connected in fastboot mode
12/025/2012 01:25:33 - INFO - Please wait device is rebooting into fastboot mode (via Fastboot)
12/025/2012 01:25:33 - INFO - Device will soon reboot back into fastboot mode
12/025/2012 01:25:34 - INFO - Device disconnected
12/025/2012 01:25:36 - INFO - Device connected in fastboot mode
12/025/2012 01:25:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\boot.img
12/025/2012 01:25:40 - INFO - Flashing selected kernel
12/025/2012 01:25:40 - INFO - FASTBOOT Output:
sending 'boot' (5850 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
Click to expand...
Click to collapse
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?
Rooting doesnt unlock the bootloader.. Is ur bootloader unlocked? how did u do it? SE has given official instructions on how to unlock the bootloader..
http://unlockbootloader.sonymobile.com/
R u trying to flash this Kernel via the Flash tool software? I would suggest you to connect ur cell in the fastboot mode.
Switch it off and connect it to PC via USB by pressing the menu button (A blue LED will be seen)
U need to have working fastboot for that..
http://www.mediafire.com/?b2of5mpqi2bwczt
Extract this file and when u'll connect ur cell to PC as stated above, for the first time, it will ask for drivers... browse to the USB driver folder which is in the .rar file.
Once u r done with the unlocking bootloader, download the kernel img file and save it in the folder where fastboot.exe is.
Now open the command promt (if u r using windows 7, just press shift and do a right click, select open command prompt here from the menu) and go to the fastboot folder in the cmd. once u r on the path of fastboot. Enter following commands :
fastboot flash boot KernelFile.img (ur copied kernel file)
it will start flashing the kernel, once it is done, type following
fastboot reboot
Ur cell be restarted, when u'll c the kernel booting, keep pressing the volume button to go into the recovery mode..
I cant be held responsible if u damage ur device!!!
Hit thanks if I helped u..
same issue
so ive tried everything i can come across to figure out why it gives me the same error. my bootloader is unlocked and phone is rooted. but i still get the phone must be rooted message no matter what i do and its so irritating cuz i want to put miui on it but cant for the life of me flash anything except stock roms. fastboot not working for me at all. any help please
edit
even though store claimed it to be unlocked the bootloader was not phone just wasnt branded to any carrier so had to unlock the bootloader and everything is glorious now:}
iKevinShah said:
I have got the same stuff (but on my xperia neo)
same exact problem.
The is nothing with bootloader or root, i guess
what my experience is, when i open with cmd in windows and type fastboot devices, i get none but in flashtool it recognised the device in fastboot.
Do you also have the same status as this ?
Click to expand...
Click to collapse
Seriously bro.. you're doing something wrong.. once install all the drivers and execute this command..
Fastboot.exe -i 0x0fce getvar version
If u get 0.3 or something its all fine..
Don't forget to hit 'THANKS' if I helped..
Sent from my Xperia Pro using XDA
You need to unlock your bootloader....
unlockbootloader.sonymobile.com/instructions
I has the same problem, after unlock bootloader, its fine!
I solve it
Overdose1986 said:
Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?
Click to expand...
Click to collapse
Hi,after "BootLoader" again,it's OK.I hope it's useful for U.
i have the same problem
it says that you device must be rooted
and i have my xperia ray rooted and unlocked bootloader
please help me to solve this problem:crying:
I cannot unlock the bootloader
I do have the same problem, my device is rooted as per doomlord method and I when I try to install a custum kernel I too get the error
failed remote the device must be rooted first.
Also I could not unlock the bootloader when I try the steps mentioned in sony website, I got the unlock code and it says " need a unlocked device" while I try to unlock the bootloader: fastboot -i 0x0fce oem unlock 0x<unlockcode>
mail_venu said:
I do have the same problem, my device is rooted as per doomlord method and I when I try to install a custum kernel I too get the error
failed remote the device must be rooted first.
Also I could not unlock the bootloader when I try the steps mentioned in sony website, I got the unlock code and it says " need a unlocked device" while I try to unlock the bootloader: fastboot -i 0x0fce oem unlock 0x<unlockcode>
Click to expand...
Click to collapse
Put the unlock code in the command, enter it, while having phone in fastboot mode, and bootloader should get unlocked. That is only if you do have SIM-unlocked phone, that is no SIM-lock.
--
same problem
Overdose1986 said:
Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?
Click to expand...
Click to collapse
same problem, who to fix?
joaoandre23 said:
same problem, who to fix?
Click to expand...
Click to collapse
Download the lastest flashtool available, now allows you to flash .img kernels
joaoandre23 said:
same problem, who to fix?
Click to expand...
Click to collapse
Rooting does not unlock your bootloader. They are not even related to each other!
There is a big difference between "Bootloader unlock allowed: Yes" and "Bootloader unlocked: Yes". I think you understand the difference.
Unlock bootloader and then try to flash kernel again.
Someguyfromhell said:
Put the unlock code in the command, enter it, while having phone in fastboot mode, and bootloader should get unlocked. That is only if you do have SIM-unlocked phone, that is no SIM-lock.
Click to expand...
Click to collapse
That's right.
The whole process look like (with my phone:
Code:
E:\Download\Mobile\Xperia>fastboot devices
CB5121CFWR&ZLP fastboot
E:\Download\Mobile\Xperia>fastboot.exe -i 0x0fce getvar version
version: 0.5
finished. total time: 0.001s
E:\Download\Mobile\Xperia>fastboot flash boot boot.img
sending 'boot' (8617 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.005s
E:\Download\Mobile\Xperia>fastboot.exe -i 0x0fce oem unlock 0xUNLOCK-KEY
...
(bootloader) Unlock phone requested
OKAY [ 0.500s]
finished. total time: 0.501s
E:\Download\Mobile\Xperia>fastboot flash boot boot.img
sending 'boot' (8617 KB)...
(bootloader) USB download speed was 20960kB/s
OKAY [ 0.438s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 0.482s]
finished. total time: 0.922s
E:\Download\Mobile\Xperia>
mandarjoshiin said:
Rooting doesnt unlock the bootloader.. Is ur bootloader unlocked? how did u do it? SE has given official instructions on how to unlock the bootloader..
http://unlockbootloader.sonymobile.com/
R u trying to flash this Kernel via the Flash tool software? I would suggest you to connect ur cell in the fastboot mode.
Switch it off and connect it to PC via USB by pressing the menu button (A blue LED will be seen)
U need to have working fastboot for that..
http://www.mediafire.com/?b2of5mpqi2bwczt
Extract this file and when u'll connect ur cell to PC as stated above, for the first time, it will ask for drivers... browse to the USB driver folder which is in the .rar file.
Once u r done with the unlocking bootloader, download the kernel img file and save it in the folder where fastboot.exe is.
Now open the command promt (if u r using windows 7, just press shift and do a right click, select open command prompt here from the menu) and go to the fastboot folder in the cmd. once u r on the path of fastboot. Enter following commands :
fastboot flash boot KernelFile.img (ur copied kernel file)
it will start flashing the kernel, once it is done, type following
fastboot reboot
Ur cell be restarted, when u'll c the kernel booting, keep pressing the volume button to go into the recovery mode..
I cant be held responsible if u damage ur device!!!
Hit thanks if I helped u..
Click to expand...
Click to collapse
can you re-upload the files you uploaded on mediafire please?
isko95 said:
can you re-upload the files you uploaded on mediafire please?
Click to expand...
Click to collapse
Can you use the search button please?
僕のINO2から送られてきた
Solved
I was having the same problem and it was due locked bootloader
then i unlocked the bootloader and every thing goes fine
so, dudes, I had the same problem... beyond others
the situation is: YOUR BOOTLOADER LOOKS LIKE UNLOCKED,
BUT IT ISN'T!!
When you rooted your phone, the rooting method modificated this notification. But the true story is that you need to go to Sony website and claim your BOOTLOADER UNLOCK CODE.
Unless you do this, you'll never flash any thing on your smartphone.
Hugs and kisses!!
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
I'm on 2.18 and rooted. Problem is, I uninstalled or disabled a bunch of ASUS apps, will I have an issue if I use SuperSU to unroot and try to restore or upgrade my phone to 2.19?
Also, I have model number ASUS_Z00AD. Is this firmware OK to install on my phone?
cmendonc2 said:
That second link is trying to run some chrome extension, not download the file?
---------- Post added at 11:35 AM ---------- Previous post was at 11:27 AM ----------
I think this is the file you were trying to link to:
https://mega.co.nz/#!IlMGiZ7I!kepXRFda7cgNPWHQovkCZaMaD2zVF4UufAJT6YEDU3k
Click to expand...
Click to collapse
Fixed.
edit: nvm...
Both download links link to the same file. splashscreen.img
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
jpacleb85 said:
Uh.. wtf? Since when has the boot loader been unlocked? I was under the impression that we were waiting for an unlock tool as has been discussed in a few threads.. is this legit?
Edit: nevermind.. I stop looking for a day or two and this device's boot loader is unlocked. I am very excited and glad that I picked this device as it seems like it is in for a lot of love
Click to expand...
Click to collapse
LOL... Gotta love the devs who tinker on here... Now we might actually get a recovery that will do nandroid backups in case of those "little" mistakes/problems that crop up from time to time...
MiCmAsTa said:
Both download links link to the same file. splashscreen.img
Click to expand...
Click to collapse
Fixed.
This is probably a silly question, but I have the ZE550ML and the latest update is 2.18, meaning that unlocking the bootloader it is still not possible can I install droidboot.img(fastboot img) from the 2.19 ZE551ML on my device? Or that will just hard brick my device?
Let me know your thoughts on this.
Continue the great work XDA crew =)
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
PsychoKilla666 said:
I am on 2.18 and can't seem to find any way to update to 2.19, all the links are dead.
so I rooted and flashed droidboot, but when i run the adb commands it says unlock failed and restarts
any help would be greatly appreciated
Click to expand...
Click to collapse
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
rafyvitto said:
You need to flash the pre rooted 2.19 system.img, then you will be able to unlock, since 2.19 has the unlock files in system.
Click to expand...
Click to collapse
Link please? and how to?
error
rafyvitto said:
Hey guys , here's a simple guide on how to unlock your bootloader without having to downgrade all the way back to 2.17, in my case i had 2.17 system since it was the most stable(2.18 is a cluster hell of bugs) with 2.18 bootloader and recovery(yes you can mix and match)and so i went to try the bootloader unlock with just flashing the 2.19 system.img, that dint do anything the "getprop ro.isn > /factory/asuskey" command would do nothing, the bootloader wasnt unlock and so i did the following:
1.Downloaded the2.19 ota manually here link
2. I extracted the droidboot.img(fastboot img) from the 2.19 ota zip
3.Rebooted to fastboot mode
4. Then ran this command "fastboot flash fastboot droidboot.img"
5,After this i rebooted back into system and rerun the unlock bootloader steps and viola the bootloader unlocked!( it wasn't before simply because the 2.18 fastboot does not have this unlock command)
6.After you unlock the bootloader your device will most likely get stuck at the bootanimation screen, at this time reboot back into fastboot mode and downloaded the black splashscreen here and run "fastboot flash splashscreen splashscreen.img". then reboot back to system and your device should boot all the way into your homescreen and your done =]
All credits go to ssj and shakalacas(ota links splashscreen link) for the bootloader unlock.
THIS WILL NOT WIPE ANYTHING ON YOUR DEVICE, if you mess up the commands thats on you follow the guide properly and everything will be fine.
Click to expand...
Click to collapse
I follow this method and received the following error on CMD
writing 'fastboot'....
FAILED (remote: falsh_cmds error!
Finished. total time: 0.830
im on 2.20 and it wont let me do anything.. i get the white boot screen instead of black but bootloader doesnt exist and it wont download twrp any suggestions?
Success
My phone's recovery stopped working, and the bootloader was locked, but I found this thread. I think I was able to get it working.
I extracted the droidboot.img from the file in the OP.
I copied the droidboot.img to my working directory, and tried to flash it.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.661s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.826s
Ok, I got the error. Maybe the "unlock" command will work.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.203s]
finished. total time: 0.204s
Same output as the last hundred times I tried to run it.
I rebooted the phone.
Code:
C:\myworkingdirectory>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.108s]
finished. total time: 0.109s
I put the phone into the bootloader mode. (For anyone reading, to get into the bootloader, turn the phone completely off. Hold the power button until it vibrates. Then hold the volume up key.)
I ran the unlock command twice.
Code:
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.291s]
finished. total time: 0.326s
C:\myworkingdirectory>fastboot oem shell_cmd "getprop ro.isn > /factory/asuskey"
...
OKAY [ 0.216s]
finished. total time: 0.216s
Then I tried to flash the image again.
Code:
C:\myworkingdirectory>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14410 KB)...
OKAY [ 0.690s]
writing 'fastboot'...
OKAY [ 0.692s]
finished. total time: 1.384s
No error?! I have progress!
------
I believe my bootloader is unlocked. Let me try to flash the recovery. (My recovery was corrupted longggg before doing this.)
Code:
C:\myworkingdirectory>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11676 KB)...
OKAY [ 0.579s]
writing 'recovery'...
OKAY [ 0.571s]
finished. total time: 1.153s
No permission error! (Before this, I would usually have gotten an error that says "FAILED (remote: Permission denied".)
---- Important Notes ----
NO WHITE BACKGROUND IN BOOTLOADER.
Many people have reported seeing an inverted background in the bootloader. I don't have that.
TRIPLE DOTS IN COMMAND PROMPT
The triple dots you see when I run the unlock command are actually there. They are not placeholders.
------------
Right now I'm booting into recovery mode to flash a ROM to the phone. I'll update if I get the phone working.
Hi, I am trying to install twrp twrp-3.1.1-0-odin.img so I can get RR rom on my C6502
first of all, I'm well aware of steps, and I personally have this rom installed in my xperia m, so it won't be hard for me to understand and it's quite easy as 123 over there
the problem I'm facing is, this xperia ZL c6502 l35h device seems to have something in different I'm not able to flash twrp here
I used repair feature in sony pc companion, done successfully, start device, wait for first boot time, configure, enable unknown source, enable usb debugging, connect cable to pc and allow RSA pc's code
power off and connect with voldown, used flash tool to unlock bootloader (yes the blootloader status unlock is yes in *#*#7378042#*#* code confi thing)
bootloader unlocked successfully, device tried to be in bootloop for three times, then it started, like first boot took somewhere 15 min to start up, and everything is fine, except I cannot increase brightness anymore but nvm
I again enable unknown source, and usb debugging, and allow my pc's RSA key > always allow
poweroff, connect in fastboot, flash kernel > select the just downloaded twrp from official source 3.1.1.0 I think
I flash receive an error says remote: command not allowed
22/002/2017 07:02:33 - INFO - Device connected in fastboot mode
22/002/2017 07:02:39 - INFO - Selected kernel (boot.img or kernel.sin): D:\IDM\General\twrp-3.1.0-0-odin.img
22/002/2017 07:02:39 - INFO - Flashing selected kernel
22/002/2017 07:02:40 - INFO - sending 'boot' (11406 KB)...
22/002/2017 07:02:40 - INFO - OKAY [ 0.361s]
22/002/2017 07:02:40 - INFO - writing 'boot'...
22/002/2017 07:02:40 - INFO - FAILED (remote: Command not allowed)
22/002/2017 07:02:40 - INFO - finished. total time: 0.363s
22/002/2017 07:02:40 - INFO - FASTBOOT Output:
sending 'boot' (11406 KB)...
OKAY [ 0.361s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.363s
tried to used minimal adb and fast boot
here's the log
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (11474 KB)...
OKAY [ 0.364s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.368s
So, I have my bootloader unlocked, I can confirm that because after booting up post unlock, there's change in system, I cannot increase brightness, and in that code *#*#7378... I see more Bands available before unlock
and device booted after like 3 bootloops automatically, what am I doing wrong, and what should I do? how are people able to get this rom in their device?
btw, I'm dealing with firmware 10.7.A.0.222 India version, all latest as per pc companion repair feature and today it will be offc latest one
and the version of my flashtool is 0.9.18.6
in minimal adb and fastboot, I tried this
fastboot.exe -i 0x0fce getvar version
result is 0.5
fastboot.exe -i 0x0fce oem unlock 0x[my key in caps]
first time it fails and second time it does, and output is successfull
then I proceed to flash twrp
fastboot flash recovery twrp.img
I receive failed command not allowed
then I try
fastboot flash boot boot.img
successful, but phone bricked
I reflash 10.7.A.0.222 and device working again, but how do I flash twrp?
what am I doing wrong?
Godlydevils said:
Hi, I am trying to install twrp twrp-3.1.1-0-odin.img so I can get RR rom on my C6502
first of all, I'm well aware of steps, and I personally have this rom installed in my xperia m, so it won't be hard for me to understand and it's quite easy as 123 over there
the problem I'm facing is, this xperia ZL c6502 l35h device seems to have something in different I'm not able to flash twrp here
I used repair feature in sony pc companion, done successfully, start device, wait for first boot time, configure, enable unknown source, enable usb debugging, connect cable to pc and allow RSA pc's code
power off and connect with voldown, used flash tool to unlock bootloader (yes the blootloader status unlock is yes in *#*#7378042#*#* code confi thing)
bootloader unlocked successfully, device tried to be in bootloop for three times, then it started, like first boot took somewhere 15 min to start up, and everything is fine, except I cannot increase brightness anymore but nvm
I again enable unknown source, and usb debugging, and allow my pc's RSA key > always allow
poweroff, connect in fastboot, flash kernel > select the just downloaded twrp from official source 3.1.1.0 I think
I flash receive an error says remote: command not allowed
22/002/2017 07:02:33 - INFO - Device connected in fastboot mode
22/002/2017 07:02:39 - INFO - Selected kernel (boot.img or kernel.sin): D:\IDM\General\twrp-3.1.0-0-odin.img
22/002/2017 07:02:39 - INFO - Flashing selected kernel
22/002/2017 07:02:40 - INFO - sending 'boot' (11406 KB)...
22/002/2017 07:02:40 - INFO - OKAY [ 0.361s]
22/002/2017 07:02:40 - INFO - writing 'boot'...
22/002/2017 07:02:40 - INFO - FAILED (remote: Command not allowed)
22/002/2017 07:02:40 - INFO - finished. total time: 0.363s
22/002/2017 07:02:40 - INFO - FASTBOOT Output:
sending 'boot' (11406 KB)...
OKAY [ 0.361s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.363s
tried to used minimal adb and fast boot
here's the log
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (11474 KB)...
OKAY [ 0.364s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.368s
So, I have my bootloader unlocked, I can confirm that because after booting up post unlock, there's change in system, I cannot increase brightness, and in that code *#*#7378... I see more Bands available before unlock
and device booted after like 3 bootloops automatically, what am I doing wrong, and what should I do? how are people able to get this rom in their device?
btw, I'm dealing with firmware 10.7.A.0.222 India version, all latest as per pc companion repair feature and today it will be offc latest one
and the version of my flashtool is 0.9.18.6
in minimal adb and fastboot, I tried this
fastboot.exe -i 0x0fce getvar version
result is 0.5
fastboot.exe -i 0x0fce oem unlock 0x[my key in caps]
first time it fails and second time it does, and output is successfull
then I proceed to flash twrp
fastboot flash recovery twrp.img
I receive failed command not allowed
then I try
fastboot flash boot boot.img
successful, but phone bricked
I reflash 10.7.A.0.222 and device working again, but how do I flash twrp?
what am I doing wrong?
Click to expand...
Click to collapse
Just to confirm that you did change your downloaded recovery name to boot.img and placed it inside c drive adb folder, right?
hhjadeja007 said:
Just to confirm that you did change your downloaded recovery name to boot.img and placed it inside c drive adb folder, right?
Click to expand...
Click to collapse
yes, I renamed to boot.img after googling and learning,
and as I had minimal adb and fastboot installed in
C:\Program Files (x86)\Minimal ADB and Fastboot
I placed in that directory
is that correct?
Godlydevils said:
yes, I renamed to boot.img after googling and learning,
and as I had minimal adb and fastboot installed in
C:\Program Files (x86)\Minimal ADB and Fastboot
I placed in that directory
is that correct?
Click to expand...
Click to collapse
Yeah that's correct.
hhjadeja007 said:
Yeah that's correct.
Click to expand...
Click to collapse
Hi, I just managed to get it done, but another problem arise
I flash anew 10.7.A.0.222
after that, I ticked unknown source, and enable debugging, and as people mentioned that it means bootloader is not unlocked
I fired this command five times
fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64
and after that I fired
fastboot flash boot boot.img
output was
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (11474 KB)...
OKAY [ 0.364s]
writing 'boot'...
OKAY [ 0.548s]
finished. total time: 0.915s
means it worked, but when I hold power button, it vibrates, if I press and hold again, it would vibrate, and never start up
if I connect it for charging red LED would blink
Godlydevils said:
Hi, I just managed to get it done, but another problem arise
I flash anew 10.7.A.0.222
after that, I ticked unknown source, and enable debugging, and as people mentioned that it means bootloader is not unlocked
I fired this command five times
fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64
and after that I fired
fastboot flash boot boot.img
output was
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (11474 KB)...
OKAY [ 0.364s]
writing 'boot'...
OKAY [ 0.548s]
finished. total time: 0.915s
means it worked, but when I hold power button, it vibrates, if I press and hold again, it would vibrate, and never start up
if I connect it for charging red LED would blink
Click to expand...
Click to collapse
Well, it's strange.
hhjadeja007 said:
Well, it's strange.
Click to expand...
Click to collapse
that's the one I'm trying
downloaded from
https://dl.twrp.me/odin/twrp-3.1.1-0-odin.img
okay, I just flashed again .222 I will now unlock bootloader, then restart and post result
Godlydevils said:
that's the one I'm trying
downloaded from
https://dl.twrp.me/odin/twrp-3.1.1-0-odin.img
okay, I just flashed again .222 I will now unlock bootloader, then restart and post result
Click to expand...
Click to collapse
Maybe try pressing vol + button just like Xperia m after mobile vibrates
hhjadeja007 said:
Maybe try pressing vol + button just like Xperia m after mobile vibrates
Click to expand...
Click to collapse
Here's something more I learned
If you unlock boot loader, and restart, > tick unknown + usb debugging, and boot to bootloader, it won't let you flash boot.img
but if you immediately unlock bootloader, and without restart, you flash boot.img, it will go success
but after that, your device won't start
it's not starting, it vibrates, but no display, no matter how many times you press and hold power button to start it, it will vibrate, and won't start
I tried each and every combination of vol +/- and power button, but it's not starting that way
EDIT:
but I can still press and hold vol up and connect cable to get in fastboot mode, after which if I try flashing twrp, i again get command not allowed, except if I try fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64 and then fastboot flash boot boot.img
after which I will get success flashing that recovery, but device won't start
Godlydevils said:
Here's something more I learned
If you unlock boot loader, and restart, > tick unknown + usb debugging, and boot to bootloader, it won't let you flash boot.img
but if you immediately unlock bootloader, and without restart, you flash boot.img, it will go success
but after that, your device won't start
it's not starting, it vibrates, but no display, no matter how many times you press and hold power button to start it, it will vibrate, and won't start
I tried each and every combination of vol +/- and power button, but it's not starting that way
EDIT:
but I can still press and hold vol up and connect cable to get in fastboot mode, after which if I try flashing twrp, i again get command not allowed, except if I try fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64 and then fastboot flash boot boot.img
after which I will get success flashing that recovery, but device won't start
Click to expand...
Click to collapse
For me, i think if you're recently to unlock your bootloader. Have you try to confirmed that your bootloader really unlocked from stock firmware? (*#*#7378423#*#*) and see about bootloader info?
If bootloader already unlocked, then you're safe to flash, And have you read any requirement to flash recovery for your device? i think it's like only work for custom rom or only work for specified version of firmware?
If device won't start, then it should from kernel problem. Try to check your custom recovery compatibility before flashing, and tell us what happen next
Nicklas Van Dam said:
For me, i think if you're recently to unlock your bootloader. Have you try to confirmed that your bootloader really unlocked from stock firmware? (*#*#7378423#*#*) and see about bootloader info?
If bootloader already unlocked, then you're safe to flash, And have you read any requirement to flash recovery for your device? i think it's like only work for custom rom or only work for specified version of firmware?
If device won't start, then it should from kernel problem. Try to check your custom recovery compatibility before flashing, and tell us what happen next
Click to expand...
Click to collapse
okay,
so few points worth mentioning
1) my bootloader is unlockable, and is unlocked, I mean in 7378423 it's written yes in root status bl unlock
2) I have received code from sony, and I can unlock it
3) the only recovery that works is https://forum.xda-developers.com/showthread.php?t=2288118 that too only after using kingroot, which gives me old philz and 2.8.7.0 twrp which are not helpful, also I tried to flash RR 7.1.2 based, phone basically gets bricked
4) I can only flash twrp or any recovery if I unlock bootloader, and without restarting I flash boot.img, if I do so, phone gets bricked
Here's the ss of BL status
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There's nothing written about requirements of twrp to flash, or rom, they just don't have, but as I have latest firmware, it should work, even nothing is written in linageos thread
I found basically few members of the community faced this problem
https://forum.xda-developers.com/xperia-zl/help/related-problems-flashing-stock-t3274520/
Godlydevils said:
okay,
so few points worth mentioning
1) my bootloader is unlockable, and is unlocked, I mean in 7378423 it's written yes in root status bl unlock
2) I have received code from sony, and I can unlock it
3) the only recovery that works is https://forum.xda-developers.com/showthread.php?t=2288118 that too only after using kingroot, which gives me old philz and 2.8.7.0 twrp which are not helpful, also I tried to flash RR 7.1.2 based, phone basically gets bricked
4) I can only flash twrp or any recovery if I unlock bootloader, and without restarting I flash boot.img, if I do so, phone gets bricked
Here's the ss of BL status
There's nothing written about requirements of twrp to flash, or rom, they just don't have, but as I have latest firmware, it should work, even nothing is written in linageos thread
Click to expand...
Click to collapse
Man Your bootloader is locked. It can be clearly seen from screen shot
hhjadeja007 said:
Man Your bootloader is locked. It can be clearly seen from screen shot
Click to expand...
Click to collapse
can you explain?
hhjadeja007 said:
Man Your bootloader is locked. It can be clearly seen from screen shot
Click to expand...
Click to collapse
Better?
Godlydevils said:
Better?
Click to expand...
Click to collapse
Yeah now you are good to go
hhjadeja007 said:
Yeah now you are good to go
Click to expand...
Click to collapse
so far, I am able to flash twrp, and I just flashed RR with gapps and mod, just got into settings wizard, will update/comment if I face any problem other than music has stopped working :/
Godlydevils said:
so far, I am able to flash twrp, and I just flashed RR with gapps and mod, just got into settings wizard, will update/comment if I face any problem other than music has stopped working :/
Click to expand...
Click to collapse
Okay, that's good. Now my questions , that is recovery based on FOTA or only normal recovery based on Boot.IMG?
Sent from my nicki using XDA Labs
Nicklas Van Dam said:
Okay, that's good. Now my questions , that is recovery based on FOTA or only normal recovery based on Boot.IMG?
Sent from my nicki using XDA Labs
Click to expand...
Click to collapse
boot.img
The problem was with the lolipop rom
Had to flash Kitkat, and unlock bootloader, no probs
Hello
my name is modou sow.in fact i have a problem with my huawei p9 lite.je wanted to put on my my phone and i did a wrong handling and because it could not walk any more.auauf mode wipe / data which ended in failure. Then I tried to install the recovery, boot, system ... but at any time I have the results:
*FAILED (remote: Command not allowed);
please help me;
I apologize for the bad English because I am Senegalese.
Hi, i installed the latest LG G5 Update (lineage-14.1-20170822-nightly-h850-signed), the first regular reboot was fine.
The second reboot has "bricked" my phone.
Please check the attached Picture from the phone.
Anyon a idea how to get back the phone to "life"??? :crying:
Thank you in advance for any assistance
MoPhat
This advise comes "as is" and with no warranty and I will not be responsible for any damages of any kind.
That's a soft brick (I wouldn't even call it a brick) and should be easy to resolve.
Did you erase data and system before flashing the ZIP file? You should always do this before flashing a new OS or did you just flash over your original LG5's OS without erasing those partitions?
Try re-downloading lineage-14.1-20170822-nightly-h850-signed and run a crc32 check on both zip files (the one you downloaded originally and the one you downloaded the second time) to see if the crc32 values match. If they don't, that would explain why you ended up in this situation (assuming you flashed the file the correct way). If you are on Windows, you can download a utility called "hashmyfiles" by NirSoft to get the crc32 along with other checksum values. If you are on linux, you can use the "crc32 lineage-14.1-20170822-nightly-h850-signed.zip" command to see the crc32 value and if values do not match, try downloading it again and do the check one more time until the values match. You can also click on the "sha256" and "sha1" links below the link you downloaded the file from and then using "hashmyfiles" you can compare the values whether they match.
Anyway, the way I personally would go with this one is try to enter Recovery mode, erase system, data (and probably boot but not necessary as the OS zip file will over write it anyway) and try again. If your recovery asks you to install root / SuperUser, you should select "No" and use LOS's official SuperUser add-ons if that's what you are after.
Thank you marco-v
I can't check the crc from the file because i have updated the latest Version with the build in update function...
I have tryed to boot in the recovery menu by pressing the power und volume down button, realising when i see the lg logo an pressing again both to (normaly) enter the recovery mode. it appears the same message
http://androidflagship.com/20275-boot-lg-g5-recovery-mode
the only menu that Comes are the "factory data reset" menu, but this makes no difference...
any further ideas?
marco-v said:
This advise comes "as is" and with no warranty and I will not be responsible for any damages of any kind.
That's a soft brick (I wouldn't even call it a brick) and should be easy to resolve.
Did you erase data and system before flashing the ZIP file? You should always do this before flashing a new OS or did you just flash over your original LG5's OS without erasing those partitions?
Try re-downloading lineage-14.1-20170822-nightly-h850-signed and run a crc32 check on both zip files (the one you downloaded originally and the one you downloaded the second time) to see if the crc32 values match. If they don't, that would explain why you ended up in this situation (assuming you flashed the file the correct way). If you are on Windows, you can download a utility called "hashmyfiles" by NirSoft to get the crc32 along with other checksum values. If you are on linux, you can use the "crc32 lineage-14.1-20170822-nightly-h850-signed.zip" command to see the crc32 value and if values do not match, try downloading it again and do the check one more time until the values match. You can also click on the "sha256" and "sha1" links below the link you downloaded the file from and then using "hashmyfiles" you can compare the values whether they match.
Anyway, the way I personally would go with this one is try to enter Recovery mode, erase system, data (and probably boot but not necessary as the OS zip file will over write it anyway) and try again. If your recovery asks you to install root / SuperUser, you should select "No" and use LOS's official SuperUser add-ons if that's what you are after.
Click to expand...
Click to collapse
So it looks like your Recovery mode is messed up too? Not sure how that might have happened unless you instructed LOS to "Update Recovery" .
Have you tried to see if you are able to enter fastboot mode and reflash your custom recovery image again and try to enter Recovery mode again? The one I use on my device (Oppo Find 7) is a TWRP image and I find it very reliable.
You can see if you can boot to Recovery by running the following command from fastboot mode (assuming you have a TWRP image)
fastboot boot twrp-x.x.x-x-h850.img
Replace x.x.x.x with the version of the file.
Tryed, result is:
Code:
C:\Temp\root_H850>fastboot boot twrp-3.1.1-0-h850.img
downloading 'boot.img'...
OKAY [ 0.430s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.451s
With "adb.exe devices" are the phone not listed
Ok, my device is locked!?!?
Code:
C:\Temp\root_H850>fastboot flash recovery twrp-3.1.1-0-h850.img
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.428s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.456s
So i have tryed to unlock the device again with the unlock key i get:
Code:
C:\Temp\root_H850>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.037s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.059s
How can i disable the " Enable OEM unlock" in the developer Settings without a gui???
Ok, fastboot works, that's good but it looks like your bootloader is locked again.
FAILED (remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Try following these instructions: https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047 and see if you can get TWRP running and if you do, you can try flashing LOS again but format data + system (you will lose all data) and if you are not careful, you might lose data on internal storage + external storage so read carefully what's displayed on the screen before going ahead.
Also: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS and this will show you how to unlock your bootloader.
---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------
I just read your post, you can try:
fastboot oem unlock
and see if it works. May be it will because it was unlocked already once but can't tell for sure.
Sorry, nothing has worked.
I will try set "upgrade error" back in the lg update tool to flash the original firmware, but i need a SERIAL or the IMEI number, how can i find this out?
Normally, IMEI numbers are located right under the battery on phones that come with removable back covers and batteries. Yours however slides out, it might be somewhere there or perhaps you can check the box / packaging. So the following command didn't work?
fastboot oem unlock
What's the error you got? The official bootloader instructions on LG's website should have worked as it supports your model. To me the only issue you seem to be having is a restricted booloader and once you unlock it, everything should be fine. This is why you can't boot into TWRP using the boot command.
Not worked, the result is:
Code:
C:\Temp\root_H850>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
I see, thx, if the LG official unlock instructions did not or no longer work followed by the instructions here https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047, I am out of ideas. Perhaps someone else can help and provide further hints.
I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.
sammd301 said:
I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.
Click to expand...
Click to collapse
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.
41rw4lk said:
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.
Click to expand...
Click to collapse
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------
sammd301 said:
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------
Click to expand...
Click to collapse
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?
41rw4lk said:
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?
Click to expand...
Click to collapse
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance
You need to blankflash, then flash the latest TMO firmware for your phone. Usually you lose baseband when you flash the wrong firmware, does it say XT1789-04 by the usb port?
sammd301 said:
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance
Click to expand...
Click to collapse
I would go through the unlock process again. Your bootloader shows flashing_locked
Uzephi said:
I would go through the unlock process again. Your bootloader shows flashing_locked
Click to expand...
Click to collapse
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>
sammd301 said:
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>
Click to expand...
Click to collapse
Can you link the flash all you used and how you flashed it?
Uzephi said:
Can you link the flash all you used and how you flashed it?
Click to expand...
Click to collapse
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
sammd301 said:
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
Click to expand...
Click to collapse
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?
I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit
sammd301 said:
I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit
Click to expand...
Click to collapse
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash
Uzephi said:
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?[/QUOTE
Yes the phone does reboot by itself after running the .bat file, But it reboot back to bootloader screen.
Click to expand...
Click to collapse
Uzephi said:
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash
Click to expand...
Click to collapse
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s
sammd301 said:
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s
Click to expand...
Click to collapse
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.
Uzephi said:
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.
Click to expand...
Click to collapse
After flashing the rom again, and getting the error " Erase successful, but not automatically formatting..." I input the fastboot command "fastboot --set-active=other" and I got back "unknown option -- set-active=other" as show in the image below. Was the syntax right?
I have been googling the errors I have received like "Erase successful, but not automatically formatting.
File system type raw not supported" to see if I can land on page that can help resolve the issue with the phone.
I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.
sammd301 said:
I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.
Click to expand...
Click to collapse
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B
Uzephi said:
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B
Click to expand...
Click to collapse
After inputting the command [ fastboot --set-active=_b ] the output I got back was [ Slot _b does not exist. supported slots are:
a
b ]
I proceed to input [ fastboot --set-active=b ] the output was [ Setting current slot to 'b' ]
So I the flashing again and input the [ fastboot --set-active=b ] again and got back [ Setting current slot to 'b' ]
I pressed the power button to start the phone from bootloader menu , the phone boot-loop with the Motorola logo as show, after 6 to 8 cycling of the boot looping with the Motorola logo the phone bootup again with T-Mobile logo. When it got home screen, I saw again that Network and cellular still not working and No IMEI number too.