Related
Hi Guys, i my Google nexus one stuck on boot screen.i had read lots of post on XDA to solve this problem but not able to solve.
My Nexus one has unlocked bootloader.
I flash recovery from fastboot and it successfully flashed.
but when i try to boot into recovery mode, device stuck on boot screen with lock symbol below, which denots unlock bootloader.
Please can any buddy tell what the problem or how can it flash custome rom into it .
Thanks .
try wipe all partition again
Code:
fastboot -w
fastboot erase recovery
fastboot reboot-bootloader
and reflash recovery
must use 4ext recovery
Edited: fixed
Replace hboot with fastboot in the above commands
Sent from my Nexus 4 using xda premium
HTC Nexus One Problems- All Self-inflicted
demkantor said:
Replace hboot with fastboot in the above commands
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Hi, First off, I'm so damn new I don't even qualify yet to be called "Noob". I bought an HTC Nexus One on eBay and it was loaded with 2.3.4. But I could not get it to update. I then took a look at the build # "3.11.405.2CL81940" with "release keys" added in a line below. Google came up with two or three hits, all starting with "Weird Build....", so I decided to get rid of it by rooting the phone. Over three days of fooling around with it and I am asking for help: after doing ALL KINDS OF THINGS (can't even remember the sequence), I'm stuck with a phone which when powered on no longer goes to the "X" splash screen but to "htc" with small yield signs with exclamation points in the four corners of the screen. The only way to power it down is to remove the battery. If I connect it to my Windows PC, it is recognized (I've downloaded the drivers, SDK Manager and AVD Manager) and I can perform certain functions using the command line within the SDK. But I can't format and start all over with a "stock" release let alone Jelly Bean which was my goal when starting all this. Additional information I can provide: when I remove the phone from the USB, the Black "htc" screen disappears and a white screen replaces it with the following: Line 1) BlackRose-Made by LeCache dl95244; line 2) STOCK 145/95/196; line 3) NEXUS ONE PV(or U)T S-off; line 4) HBOOT 7.3.5.5017 (PB9910000); line 4) TOUCHPANEL SYNT0103; line 5) RADIO-5.12.00.00; line 6) Apr 21 2012, 04:53:16; line 7) RUU. Line one, "BlackRose...", is black with white characters. Lines 2-6 are green characters on a white background (resembling the old boot screen) and finally, line 7, the "RUU" characters are white in an orange background, as though it's highlighted, asking for something. As said above, no buttons work (Track ball, Vol up/Vol down), and this is where the battery has to be pulled to power it down. Can anyone help?? I'll do my best to reply with any specifics that I DO remember, but I've done so many, many things in the past three days I've lost track. Thanks.
When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium
In response to your question:
demkantor said:
When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Let me describe it from the start. After insuring the device is fully charged I power it off the only way I can, pulling the battery, waiting 5 seconds, then reassembling the battery and back.
I get out the USB cord and insert it into the Windows PC. Then, (either powered on BEFORE insertion of the Micro USB or AFTER), when the device is powered on it goes to a new splash screen with "htc" in white on a gray/black background with caution signs at each corner of the screen. The device will stay that way for hours, plugged into a PC or powered on without tethering. THE ONLY WAY to access the white screen (which resembles the old boot screen without skateboards) is to unplug the device from the USB/PC WHILE POWERED ON.
When you do this, you have the "BlackRose" in white on a black line, then the rest as described, with "RUU" in orange.
There is one additional detail I do remember doing: I downloaded and installed "HTC One (M7//T-Mobile/AT&T/Sprint) AIO Kit by Hasoon2000v2.1 and Flashed CWM (GSM Only) Recovery. That was the last time the screen was at all responsive: lot's of lines rolling upward and then the words, I think, "Update failed".
Hasoon2000, I believe, is a member of this Forum and lives in Orland Park, IL, a suburb frustratingly close to me, in Chicago!!
---------- Post added at 07:02 AM ---------- Previous post was at 06:55 AM ----------
demkantor said:
When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?
And really no buttons work at all?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Short answer, yes: Device Manager recognizes it and I hear a "cer-chunk" when its plugged in.
now you can enter bootloader or not?
bootloader
hxq88 said:
now you can enter bootloader or not?
Click to expand...
Click to collapse
Yes. I can access bootloader. Just finished the following:
fastboot device HT0ALP801351
---------- Post added at 09:29 AM ---------- Previous post was at 09:09 AM ----------
rickz41 said:
Yes. I can access bootloader. Just finished the following:
fastboot devices HT0ALP801351
Click to expand...
Click to collapse
OKAY [ 4.628s]
formatting 'userdata' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 2.230s]
formatting 'cache' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.019s]
finished. total time: 6.903s
C:\android-sdk\platform-tools>fastboot erase r
erasing 'recovery'...
OKAY [ 0.097s]
finished. total time: 0.099s
C:\android-sdk\platform-tools>
its ok . did you run commands in post #2?
let try full wipe all and try it from beginning 1 more time. or use PASSIMG method to fast restore stock rom.
edit: ok full wiped, now reflash recovery ( try 4ext or TWRP, sorry i dont know link, you can find in search forum )
Post 2
rickz41 said:
Yes. I can access bootloader. Just finished the following:
fastboot device HT0ALP801351
---------- Post added at 09:29 AM ---------- Previous post was at 09:09 AM ----------
OKAY [ 4.628s]
formatting 'userdata' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 2.230s]
formatting 'cache' partition...
Erase successful, but not automatically format
Can't determine partition type.
OKAY [ 0.019s]
finished. total time: 6.903s
C:\android-sdk\platform-tools>fastboot erase r
erasing 'recovery'...
OKAY [ 0.097s]
finished. total time: 0.099s
C:\android-sdk\platform-tools>
Click to expand...
Click to collapse
Was following your guide in post 2, yes. It accepted the first two commands but the third, "fastboot reboot bootloader" caused the terminal window to only scroll my options. I don't know what you call that but I think it means it did not work.
rickz41 said:
Was following your guide in post 2, yes. It accepted the first two commands but the third, "fastboot reboot bootloader" caused the terminal window to only scroll my options. I don't know what you call that but I think it means it did not work.
Click to expand...
Click to collapse
wrong command: it must be fastboot reboot-bootloader
command
hxq88 said:
wrong command: it must be fastboot reboot-bootloader
Click to expand...
Click to collapse
Success!!
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.028s]
finished. total time: 0.029s
C:\android-sdk\platform-tools>
(Phone powered off- heard PC disconnect then reconnect, now screen is still same: whit "htc", black background with caution marks, all four corners....
enter bootloader again and reflash recovery cuz all was wiped. but after wipe phone will auto-enter bootloader, i never see htc caution before.
let try reflash recovery ( 4ext or TWRP ) hope it will work.( with my phone, it somtimes stuck if i enter recovery after flash, just turn off the phone, wait 5-10 mins, idont know why )
edit: its the name of recovery, i miss some letter cuz fast type
additional info
hxq88 said:
enter bootloader again and reflash recovery cuz all was wiped. but after wipe phone will auto-enter bootloader, i never see htc caution before.
let try reflash recovery ( 4ext or TWRP ) hope it will work.( with my phone, it somtimes stuck if i enter recovery after flash, just turn off the phone, wait 5-10 mins, idont know why )
Click to expand...
Click to collapse
Here I must repeat, I am not even Newbie or Noob- I am less than Noob!! What is 4ext, TWRP?? I will download them and do as you say but give detailed instructions for I am only an infant!! (when it comes to this, at least!)
---------- Post added at 10:55 AM ---------- Previous post was at 10:09 AM ----------
THANK YOU SO VERY MUCH FOR GETTING ME THIS FAR!!
It is greatly appreciated.
I will leave for awhile now, but thank you again.
Those are recoveries, personally 4ext tends to be the best for all phones I've used it in but for some reason I have had issues with this on my n1, the only recovery that has never given me an issue on the n1 is amonra so that's what I use, feel free to use what you like.
That screen you were stuck in earlier is RUU mode which is meant to be used flashing official HTC RUUs, I don't think you will have an serious issues, just follow directions posted earlier
fastboot erase system -w
fastboot erase boot
fastboot flash recovery recovery.img
Then scroll to recovery option in bootloader to go into whatever recovery you chose and the flash a compatible ROM at this point
If you want to learn more about fastboot see here
http://forum.xda-developers.com/showthread.php?p=41374534
Sent from my Nexus 4 using xda premium
Progress thus far:
demkantor said:
Those are recoveries, personally 4ext tends to be the best for all phones I've used it in but for some reason I have had issues with this on my n1, the only recovery that has never given me an issue on the n1 is amonra so that's what I use, feel free to use what you like.
That screen you were stuck in earlier is RUU mode which is meant to be used flashing official HTC RUUs, I don't think you will have an serious issues, just follow directions posted earlier
fastboot erase system -w
fastboot erase boot
fastboot flash recovery recovery.img
Then scroll to recovery option in bootloader to go into whatever recovery you chose and the flash a compatible ROM at this point
If you want to learn more about fastboot see here
http://forum.xda-developers.com/showthread.php?p=41374534
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you for joining in and I must say at that I am in complete agreement with your feelings re: apple/MAC/iOS, etc.: they can go to Hell.
Let me post the results after following your instructions above:
C:\android-sdk\platform-tools>fastboot erase system -w
erasing 'system'...
OKAY [ 3.406s]
erasing 'userdata'...
OKAY [ 4.608s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.023s]
erasing 'cache'...
OKAY [ 2.223s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
Can't determine partition type.
OKAY [ 0.022s]
finished. total time: 10.293s
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.054s]
finished. total time: 0.057s
C:\android-sdk\platform-tools>fastboot flash recovery recovery-RA-passion-v2.2.1
.img
sending 'recovery' (3366 KB)...
OKAY [ 0.483s]
writing 'recovery'...
OKAY [ 1.082s]
finished. total time: 1.570s
But the n1 is still showing the gray/black splash with htc and the caution/yield signs at the corner. The line: "Erase successful, but not automatically formatting. Can't determine partition type." when erasing user data and formatting cache, is this something to be looked into?
I've flashed, I believe, successfully, AmonRa before but when I try to flash a 'Stock' passion image, it fails.
I'll continue reading your most helpful guides and hope for a step-by-step reply- I feel as though I am very close to solving this!
Again, many thanks!
Update
Sorry to report I've not made any progress since my last post despite the Guides provided.
A couple important points:
a) I cannot enter to cmd prompt level, fir whatever reason
b) This leave me with Fastboot and when the device is again wiped and prepared, Fastboot is entered, and I type Fastboot update update.zip with the following results attempting different "Stock Passion Images":
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 7.35.5017
Baseband Version.....: 5.12.00.08
Serial Number........: HT0ALP801351
--------------------------------------------
checking mid...
OKAY [ 0.003s]
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is '7.35.5017'.
Update requires '0.35.2017' or '0.35.0017'.
finished. total time: 0.047s
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools>fastboot update update.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 7.35.5017
Baseband Version.....: 5.12.00.08
Serial Number........: HT0ALP801351
--------------------------------------------
checking mid...
OKAY [ 0.003s]
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is '7.35.5017'.
Update requires '0.35.2017' or '0.35.0017'.
finished. total time: 0.047s
Any further thoughts??
Also, USB debugging is OFF complicating thins a lot, preventing me from getting a token from HTC's site!!
Bootloader should be unlocked being you have black rose, try different RUUs
http://forum.xda-developers.com/showthread.php?p=7495397
You may also try to change your cid to 11111111 this will allow you to flash any version
Sent from my Nexus 4 using xda premium
Questions:
How would I change cid ?
I've been searching the universe for RUU's and came up with one:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe . That's it. in your link I see a number of Factory Images. Which would you suggest?
---------- Post added at 03:03 PM ---------- Previous post was at 02:48 PM ----------
rickz41 said:
How would I change cid ?
I've been searching the universe for RUU's and came up with one:
RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199308_signed.exe . That's it. in your link I see a number of Factory Images. Which would you suggest?
Click to expand...
Click to collapse
Took the advice here:
http://forum.xda-developers.com/showthread.php?t=2264322
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files\Android\android-sdk\platform-tools>fastboot devices
HT0ALP801351 fastboot
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem readcid
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files\Android\android-sdk\platform-tools>
---------- Post added at 03:20 PM ---------- Previous post was at 03:03 PM ----------
C:\Program Files\Android\android-sdk\platform-tools>cd c:\mini-adb
The system cannot find the path specified.
C:\Program Files\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Program Files\Android\android-sdk\platform-tools>adb reboot bootloader
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>fastboot devices
HT0ALP801351 fastboot
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvarcid
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 7.35.5017
(bootloader) version-baseband: 5.12.00.08
(bootloader) version-cpld: None
(bootloader) version-microp: 0c15
(bootloader) version-main: 2.16.405.1
(bootloader) serialno: HT0ALP801351
(bootloader) product: nexusone
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9910000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4162mV
(bootloader) partition-layout: STOCK-145/95/196
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 0c3a097c
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.024s
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem writecid 111111
11
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files\Android\android-sdk\platform-tools>fastboot oem writecid 111111
11
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 7.35.5017
(bootloader) version-baseband: 5.12.00.08
(bootloader) version-cpld: None
(bootloader) version-microp: 0c15
(bootloader) version-main: 2.16.405.1
(bootloader) serialno: HT0ALP801351
(bootloader) product: nexusone
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9910000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4162mV
(bootloader) partition-layout: STOCK-145/95/196
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 0c3a097c
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.019s
C:\Program Files\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.026s
C:\Program Files\Android\android-sdk\platform-tools>
It rebooted back to the same ole' 'htc' screen!
Try
fastboot oem getvar cid
To read it and
fastboot oem write cid 11111111
To write
As for which ruu to pick I'm not sure, never ran one on my n1, I did see a thread not to long ago where someone was trying to grab every official update from HTC, you can also try HTC directly and try to find the latest one
Sent from my Nexus 4 using xda premium
Hello, am new at this, but I really need some assistance, I wipe my M7 but I cannot reinstall a new rom, first my computer said that it cannot find the android 1.0 driver, I try using pdanet but requested me to active the debugging option that is inside the OS but i dont have one, can someone help, also I try to send a file from my computer to the device but keeps saying it cant, am assuming cause the driver failure, I already have TWRP, unlocked and superus, can someone guide me, also am not that smart if you please keep simply instruction will be great, appreciated
adrianponce said:
Hello, am new at this, but I really need some assistance, I wipe my M7 but I cannot reinstall a new rom, first my computer said that it cannot find the android 1.0 driver, I try using pdanet but requested me to active the debugging option that is inside the OS but i dont have one, can someone help, also I try to send a file from my computer to the device but keeps saying it cant, am assuming cause the driver failure, I already have TWRP, unlocked and superus, can someone guide me, also am not that smart if you please keep simply instruction will be great, appreciated
Click to expand...
Click to collapse
Usb debugging is only needed to get adb commands working from a booted OS. You don't need to have USB Debugging turned on to use adb commands from TWRP. Anyway pdanet will not work from twrp...
You'll need to install the right drivers so you can use adb commands (form TWRP) and fastboot commands (from bootloader) to fix your phone.
Download and install the latest driver version for HTC: http://www.mediafire.com/download/1ulx1xl5k1zhk5j/HTC_Driver_4.17.0.001.exe
Once done, connect your phone to your computer and reboot it in bootloader mode. Make sure that you can see "fastboot usb" highlighted in red (like in this picture). If yes, open a command window from your computer adb/fastboot folder and type "fastboot getvar all" (without the quotes) and hit enter. Copy/paste the output here so we can know a little more about your phone and how to help you get the correct rom on it (remove your IMEI and SERIALNO before posting).
Btw do you want it to run a stock or custom rom? What is your TWRP version?
"alray" I download the drivers and install them, I connected the phone in fastboot and is highlighted red with the usb as well, I open the command center and type "fastboot getvar all", but it says waiting for any device, and stays there does not do anything, I wait almost 30 minutes and nothing, am i doing something wrong?, thanks
apparently even after installing the drivers, the device manager still not recognize my phone, although in the fastboot bootloader says usb, I do not know how to insert and image about my device manager, phone and installation programs, sorry
"alray", finally got it, is used this link http://forum.xda-developers.com/showthread.php?p=48915118#post48915118, version 1.3, and drivers were installed correctly, this is the information you requested me,
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.51
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4289mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-46c17580
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.180s
Regarding the rom, I dont have any preference, I even not know the difference, can you recommend me one?, and TWRP version 3.0.2-0, now what would be the next step?, thanks
@alray [alray][/alray], which rom should I install and how, I try to download htc gen unlock, dev edition unlock, and once connected to the phone in fastboot usb, using command fastboot update "*.zip (zip file I download)", but says that "error: update package 'C:\fastboot\m7wlv-3.4.10-g7875f0c.zip' has no android-info.txt", should I install a different one?, thanks
@alray [alray][/alray], which rom should I install and how, I try to download htc gen unlock, dev edition unlock from http://www.htcdev.com/devcenter/downloads, and once connected to the phone in fastboot usb, using command fastboot update "*.zip (zip file I download)", but says that "error: update package 'C:\fastboot\m7wlv-3.4.10-g7875f0c.zip' has no android-info.txt", should I install a different one?, thanks
adrianponce said:
@alray [alray][/alray], which rom should I install and how, I try to download htc gen unlock, dev edition unlock from http://www.htcdev.com/devcenter/downloads, and once connected to the phone in fastboot usb, using command fastboot update "*.zip (zip file I download)", but says that "error: update package 'C:\fastboot\m7wlv-3.4.10-g7875f0c.zip' has no android-info.txt", should I install a different one?, thanks
Click to expand...
Click to collapse
This file is not for your phone, better to delete it you'll not need it.
I would suggest that you flash a RUU, this will get back your phone to the stock rom. The process is a little different from flashing a rom from TWRP but imo, the result is better.
download htc_fastboot.exe and save it in the same folder where you already have adb.exe and fastboot.exe
Download this RUU and save it in the same folder where you already have adb.exe, fastboot.exe and htc_fastboot.exe
Note that there is currently maintenance on the website hosting these files, if you can't download the files wait a few hours and try again.
Connect your phone to your computer, reboot it in bootloader mode and make sure "fastboot usb" is highlighted in red
Start a command window from your adb/fastboot folder
Type:
Code:
fastboot oem rebootRUU
Your phone will reboot in RUU mode, a black screen with silver HTC logo.
Type
Code:
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
Wait for the file to be flashed (it will take several minutes).
Once the RUU is sucesfully flashed reboot the phone using this command:
Code:
fastboot reboot
Note that the first boot after flashing a RUU can take a little more time than usual.
Btw sorry for the delay, got a problem here just after replying to your PM.
alray said:
This file is not for your phone, better to delete it you'll not need it.
I would suggest that you flash a RUU, this will get back your phone to the stock rom. The process is a little different from flashing a rom from TWRP but imo, the result is better.
download htc_fastboot.exe and save it in the same folder where you already have adb.exe and fastboot.exe
Download this RUU and save it in the same folder where you already have adb.exe, fastboot.exe and htc_fastboot.exe
Note that there is currently maintenance on the website hosting these files, if you can't download the files wait a few hours and try again.
Connect your phone to your computer, reboot it in bootloader mode and make sure "fastboot usb" is highlighted in red
Start a command window from your adb/fastboot folder
Type:
Code:
fastboot oem rebootRUU
Your phone will reboot in RUU mode, a black screen with silver HTC logo.
Type
Code:
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
Wait for the file to be flashed (it will take several minutes).
Once the RUU is sucesfully flashed reboot the phone using this command:
Code:
fastboot reboot
Note that the first boot after flashing a RUU can take a little more time than usual.
Btw sorry for the delay, got a problem here just after replying to your PM.
Click to expand...
Click to collapse
@alray, problem for the time you are the one helping me, this is what the command center gave me after I fallow your instructions
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.
51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
FAILED (data transfer failure (Unknown error))
finished. total time: 7.361s
What should I do?
@alray, I did it again a few time and like twice change the notification to the follow
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.043s
C:\fastboot>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.
51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
OKAY [ 65.303s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 65.507s
adrianponce said:
@alray, I did it again a few time and like twice change the notification to the follow
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.043s
C:\fastboot>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.
51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
sending sparse 'zip' (1478648 KB)...
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 174334115 is not a multiple of t
he block size 4096
OKAY [ 65.303s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 65.507s
Click to expand...
Click to collapse
Sorry my bad, the command is
Code:
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.
51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
Note that the difference is "htc_fastboot" instead of "fastboot"
Sent from my HTC One using XDA Labs
adrianponce said:
Hello, am new at this, but I really need some assistance, I wipe my M7 but I cannot reinstall a new rom, first my computer said that it cannot find the android 1.0 driver, I try using pdanet but requested me to active the debugging option that is inside the OS but i dont have one, can someone help, also I try to send a file from my computer to the device but keeps saying it cant, am assuming cause the driver failure, I already have TWRP, unlocked and superus, can someone guide me, also am not that smart if you please keep simply instruction will be great, appreciated
Click to expand...
Click to collapse
Hello bud. I'm quiet experienced with the HTC One (M7) and would be more the happy to help you with your issue. Are you trying to update to the latest HTC firmware or lollipop?
¤-TIP FROM THE NOOB-¤-¤-
1. enable USB Debugging before flashing custom recovery.
2. back up system before granting apk's root permission, editing system files, and flashing a new rom.
? better safe than sorry ?
?May the Angels lead your way Tom (Tony Stark) . You will be missed bud ?
Tony the noob :D said:
Hello bud. I'm quiet experienced with the HTC One (M7) and would be more the happy to help you with your issue. Are you trying to update to the latest HTC firmware or lollipop?
¤-TIP FROM THE NOOB-¤-¤-
1. enable USB Debugging before flashing custom recovery.
2. back up system before granting apk's root permission, editing system files, and flashing a new rom.
? better safe than sorry ?
?May the Angels lead your way Tom (Tony Stark) . You will be missed bud ?
Click to expand...
Click to collapse
Glad you are joining the discussion cause I'll eventually leave to work. OP should be able to flash the RUU with your help, just forgot to mention that he/she had to use htc_fastboot for flashing the RUU hence the "Invalid sparse file format" error (See post above yours).
Btw no offense intended but I think tip #1 is leading to confusion. USB debugging is not required to flash a custom recovery nor it is required to use adb from recovery. USB debugging is only enabling ADB access from a booted rom...:good:
alray said:
Glad you are joining the discussion cause I'll eventually leave to work. OP should be able to flash the RUU with your help, just forgot to mention that he/she had to use htc_fastboot for flashing the RUU hence the "Invalid sparse file format" error (See post above yours).
Btw no offense intended but I think tip #1 is leading to confusion. USB debugging is not required to flash a custom recovery nor it is required to use adb from recovery. USB debugging is only enabling ADB access from a booted rom...:good:
Click to expand...
Click to collapse
I know. Just been told. Sudo fastboot flash recovery.img is needed to flash it. I'm pro HTC and never found the reason why to enable it in system settings
Sent from my latest and greatest HTC One M7 UL
-¤-¤-TIP FROM THE NOOB-¤-¤-
1. enable USB Debugging before flashing custom recovery.
2. Create system back-up before granting apk's root permission, editing system files, and flashing a new rom.
? better safe than sorry ?
?May the Angels lead your way Tom (Tony Stark) . You will be missed bud ?
@alray @Tony the noob :D, first thanks for your help, just want to mention that I run the htc_fastboot,
C:\fastboot>htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.1
401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 7.19.401.51
found large-zip header, file count: 5
processing file 1/5...
But it stock there, been like 30 minutes, and my phone got out of the HTC gray logo, and now is in the white screen loader, but instead of saying fastboot and all that stuff, only says RUU, is that ok?
@alray @Tony The noob ,after cleaning the cache and try it again this is the notification
C:\fastboot>htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.
401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 7.19.401.51
found large-zip header, file count: 5
processing file 1/5...
sending 'zip' (50228 KB)...
OKAY [ 3.136s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 4.900s
preupdate done, rebooting...
resending command...
sending 'zip' (50228 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 10.441s
htc_fastboot finished. total time: 26.124s
@alray @Tony the noob :D, after trying few time more, finally I could, I just want to say appreciated for all the directions you gave me.
adrianponce said:
@alray @Tony the noob :D, after trying few time more, finally I could, I just want to say appreciated for all the directions you gave me.
Click to expand...
Click to collapse
Good to hear that. If you need any other assistance, please post or send me PM.
Sent from my latest and greatest HTC One M7 UL
-¤-¤-TIP FROM THE NOOB-¤-¤-
Create system back-up before granting apk's root permission, editing system files, and flashing a new rom.
? better safe than sorry ?
?May the Angels lead your way Tom (Tony Stark) . You will be missed bud ?
I was following this guide in order to update my formerly rooted bootloader unlocked Nexus 6. I've been able to follow those instructions in the past to update my phone, but something went wrong this time. I'm on the MMB29Q version, so I downloaded the MMB29Q to MMB29V update, the link to which I found on this site. I also downloaded the MMB29Q factory image from Google's list of them and extracted the system.img file. My phone has the stock recovery, and my computer is on Arch Linux with adb version 1.0.36 and fastboot version 7.1.2_r6.
I was able to erase the system image easily enough:
Code:
$ ~ adb reboot bootloader
$ ~ fastboot erase system
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.673s]
finished. total time: 0.673s
However, when I then tried to flash the system image,
Code:
$ ~ fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (518702 KB)...
OKAY [ 16.242s]
writing 'system' 1/4...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.250s
it failed on me. According to the bootloader splash screen, my "Device is UNLOCKED. Status Code: 3" (I read somewhere that the Preflash validation failed message corresponds with an unlocked bootloader).
One other thing to note is that I remember leaving the checkbox for allowing oem unlock in developer options unchecked, which I am now realizing was probably where I went wrong (I ran fastboot oem unlock as a test, and it told me to Check 'Allow OEM Unlock' in Developer Options). However, because I cleared the system image, I don't know how I can change that setting anymore. I also realize that I didn't need to do this step in the updating process because my phone was already unrooted and thus system.img should have been stock (I think, at least). I tried re-erasing the system image and reflashing it, but that unfortunately did not fix anything. Any advice would be much appreciated!
Progress! I was able to flash TWRP, back up all my data just in case, and then follow this guide, which toggles the "Allow OEM Unlock" developer settings without having a working operating system. Running fastboot oem unlock no longer gives the error about checking that box in Settings. However, I'm still getting that same error when I try to flash the system.img. After that failed, I am fresh out of ideas, given that the problem does not seem to be that option. Anyone have any ideas?
Edit: I now realize I am a moron. I found this thread on Android.SE and realized that I had in fact downloaded the Nexus 6P MMB29Q version and that is why it failed. After downloading the correct verion, rewiping the system partition, and reflashing it, my phone works again!
Hi Folks,
Need some help here. I'm new to flash and other stuff.
I tried to install Lineage 15.1. I did fastboot oem unlock which erased everything. I'm stuck in AP fastboot Flash Mode.
I tried below things.
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash system lineage-15.1-20180402-nightly-shamu-signed.zip
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 18.385s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 18.400s
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash recovery twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.422s]
booting...
OKAY [ 0.031s]
finished. total time: 0.469s
[PHONE GETS TWRP RECOVERY SCREENS]
I tried adb sideload as suggested in one of the pages and got this
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload lineage-15.1-20180402-nightly-shamu-signed.zip
Total xfer: 0.01x
In Phone :
Starting ADB sideload feature ..
Installing zip file '/sideload/package.zip'
Warning: No file_contexts
Target : google/shamu/shamu:7.1.1/N6F27m/4299435:user/release-keys
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: Failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid Argument
Failed to unmount /system : No such volume
script aborted (no error message)
Updater process ended with ERROR: 7
Finally, I tried with copying installer files in OTG Drive and tried to install from there. But couldn't mount it as I can't make OTG check in Mount in TWRP.
Please help .. How can I overcome this and install OS in my phone.
Can you boot into twrp?? When i flashed my shamu first time...i unlocked bootloader, flashed twrp, rooted and then via twrp flashed roms from zips, gapps and magisk. As far as i remember. Otg is some times really tricky...i tried several usb sticks and suddenly one worked and i got forward in flashing. Nowadays my pc recognise my shamu in twrp and i can move files in it (if needed). Hope that helps.
mal13 said:
Can you boot into twrp?? When i flashed my shamu first time...i unlocked bootloader, flashed twrp, rooted and then via twrp flashed roms from zips, gapps and magisk. As far as i remember. Otg is some times really tricky...i tried several usb sticks and suddenly one worked and i got forward in flashing. Nowadays my pc recognise my shamu in twrp and i can move files in it (if needed). Hope that helps.
Click to expand...
Click to collapse
Yes, I can boot into twrp using this command...
fastboot.exe boot twrp-3.2.1-0-shamu.img
This bringstwrp in my phone. But I can't move files to the phone. Even I tried adb push which pushes the files to the phone but while installing it got failed.. I'm not sure what I'm missing..
I think the problem is the fastboot you are using is not compatible with shamu. See if this minimal install works any better; [TOOL]Minimal ADB and Fastboot. Try one of the older releases, maybe 1.4 or 1.3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I think the problem is the fastboot you are using is not compatible with shamu. See if this minimal install works any better; [TOOL]Minimal ADB and Fastboot. Try one of the older releases, maybe 1.4 or 1.3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Same issue with Minimal ADB. I used 1.4 ...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-shamu.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-15.1-20180402-nightly-shamu-signed.zip
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 15.628s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 15.644s
vigkumar said:
Same issue with Minimal ADB. I used 1.4 ...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-shamu.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-15.1-20180402-nightly-shamu-signed.zip
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 15.628s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 15.644s
Click to expand...
Click to collapse
Looks to me that my filesystem on is corrupt. Is there any commands to fix the filesystem. I tried with repair in TWRP but that is also not working.
vigkumar said:
Looks to me that my filesystem on is corrupt. Is there any commands to fix the filesystem. I tried with repair in TWRP but that is also not working.
Click to expand...
Click to collapse
When in doubt, my philosophy is to return to stock and start over. If you have any data on the user data partition, back it up through ADB and then try fastboot flashing the last google stock ROM. The instructions (if you need them) are on the Factory Image page. If Fastboot still fails, you can try sideloading through ADB an Full OTA.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
When in doubt, my philosophy is to return to stock and start over. If you have any data on the user data partition, back it up through ADB and then try fastboot flashing the last google stock ROM. The instructions (if you need them) are on the Factory Image page. If Fastboot still fails, you can try sideloading through ADB an Full OTA.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Thank you very much for your response. I tried both Fastboot and ADB. Both failed Well, I suppose if I could flash the right radio 'D4.01-9625-05.45+FSG-9625-02.117', I guess Fastboot would work. Am I right.
What is the right way to identify the correct radio file.
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is 'D4.01-9625-05.51+FSG-9625-02.118'.
Update requires 'D4.01-9625-05.45+FSG-9625-02.117'.
finished. total time: 0.094s
ADB devices produces nothing. Hence I booted in twrp and use ADB sideload from there.
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
OKAY [ 0.038s]
finished. total time: 0.469s
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload shamu-ota-n6f27m-df27bd83.zip
Total xfer: 0.01x
Even it got failed with the below error.
Installing zip file '/sideload/package.zip'
Target: google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater Process ended with Error 7.
vigkumar said:
Thank you very much for your response. I tried both Fastboot and ADB. Both failed Well, I suppose if I could flash the right radio 'D4.01-9625-05.45+FSG-9625-02.117', I guess Fastboot would work. Am I right.
What is the right way to identify the correct radio file.
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is 'D4.01-9625-05.51+FSG-9625-02.118'.
Update requires 'D4.01-9625-05.45+FSG-9625-02.117'.
finished. total time: 0.094s
ADB devices produces nothing. Hence I booted in twrp and use ADB sideload from there.
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
OKAY [ 0.038s]
finished. total time: 0.469s
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload shamu-ota-n6f27m-df27bd83.zip
Total xfer: 0.01x
Even it got failed with the below error.
Installing zip file '/sideload/package.zip'
Target: google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater Process ended with Error 7.
Click to expand...
Click to collapse
Radio makes no difference. You can run any radio from any release on any release. It affects only the data/cell connection and sometimes an older one forces better performance depending on carrier and location.
Try fastboot flashing with the sim card removed.
The manual steps to flash through fastboot are in the [GUIDE][HOW TO] Flash Factory Images thread. Scroll down to "Method 2 : (Long, but works always)".
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
vigkumar said:
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash system lineage-15.1-20180402-nightly-shamu-signed.zip
Click to expand...
Click to collapse
That was your first error! You can't flash a nightly via fastboot.
You need to boot into recovery and select it there to install.
ktmom said:
Radio makes no difference. You can run any radio from any release on any release. It affects only the data/cell connection and sometimes an older one forces better performance depending on carrier and location.
Try fastboot flashing with the sim card removed.
The manual steps to flash through fastboot are in the [GUIDE][HOW TO] Flash Factory Images thread. Scroll down to "Method 2 : (Long, but works always)".
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Both method failed. :crying::crying:
vigkumar said:
Both method failed. :crying::crying:
Click to expand...
Click to collapse
You are trying to fastboot flash the STOCK ROM I linked to earlier, right?
As @Elektroschmock pointed out -and I originally missed- your first mistake was trying to fastboot flash the lineage ROM. You also CAN NOT ADB sideload anything except the OTA stock image linked to earlier. That includes the stock ROM used to fastboot flash, or any custom ROM.
** If ** you really are trying to fastboot flash stock, and it doesn't work, what does:
Code:
fastboot devices
return?
The N6 is a simple device to work with and very forgiving, but you must use common sense and think about what your doing.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
You are trying to fastboot flash the STOCK ROM I linked to earlier, right?
As @Elektroschmock pointed out -and I originally missed- your first mistake was trying to fastboot flash the lineage ROM. You also CAN NOT ADB sideload anything except the OTA stock image linked to earlier. That includes the stock ROM used to fastboot flash, or any custom ROM.
** If ** you really are trying to fastboot flash stock, and it doesn't work, what does:
Code:
fastboot devices
return?
The N6 is a simple device to work with and very forgiving, but you must use common sense and think about what your doing.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Yes, I'm trying stock and followed links that you provided. Both installation methods failed.
Fastboot devices returns,
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot devices
ZX1G525DZX fastboot
Extract the zip file downloaded from the factory image page. For example, downloaded file is "shamu-n6f27h-factory-718e138f.zip" then when extracted I get a folder "shamu-n6f27h".
Navigate into the extracted folder (e.g "shamu-n6f27h")
Now copy the radio-shamu-XXXXXX.img (the x's are placeholders it depends on the radio version) to the location where your fastboot is then rename it to just "radio.img"
Back in the originally extracted folder ("shamu-n6f27h"), there will be another zip file, in my example it's "image-shamu-n6f27h.zip". Extract that and I end up with a folder "image-shamu-n6f27h".
Now copy the following files from the new folder (e.g. "image-shamu-n6f27h") to the location where your fastboot is;
boot.img
cache.img
recovery.img
system.img
userdata.img
Navigate on the PC to the location where the fastboot binary is.
Boot the phone into fastboot by pushing and holding the volume down and power buttons
Look on the phone's screen and there should be a message "Device is unlocked. Status Code 3" confirming the bootloader is unlocked.
Double check that "fastboot devices" returns your device.
Now type "fastboot reboot-bootloader", which will power off the phone and start it again in the same place. Just double checking that you are communicating correctly with the device.
Code:
1) flash the boot image (also called the kernel):
fastboot flash boot boot.img
reboot:
fastboot reboot-bootloader
2) If you want, you can flash the radio:
fastboot flash radio radio.img
reboot:
fastboot reboot-bootloader
3) flash recovery:
fastboot flash recovery recovery.img
reboot:
fastboot reboot-bootloader
4) flash system partition:
fastboot flash system system.img
reboot:
fastboot reboot-bootloader
5) flash userdata (which will wipe the internal storage:
fastboot flash userdata userdata.img
reboot:
fastboot reboot-bootloader
6) flash cache:
fastboot flash cache cache.img
Now we are done flashing all of the partitions on a N6 so reboot to system:
fastboot reboot
If any of these fail, or don't match what I described above, post the exact errors here, preferably formatted within CODE tags. They look like: [ CODE ] [ / CODE ] without any spaces inside the brackets. The spaces are necessary to prevent the forum from executing the example as formating tags.
Posting "it doesn't work" may be funny, but it does nothing to help others help you. You must be specific as to what you were doing and what happened.
ktmom said:
Extract the zip file downloaded from the factory image page. For example, downloaded file is "shamu-n6f27h-factory-718e138f.zip" then when extracted I get a folder "shamu-n6f27h".
Navigate into the extracted folder (e.g "shamu-n6f27h")
Now copy the radio-shamu-XXXXXX.img (the x's are placeholders it depends on the radio version) to the location where your fastboot is then rename it to just "radio.img"
Back in the originally extracted folder ("shamu-n6f27h"), there will be another zip file, in my example it's "image-shamu-n6f27h.zip". Extract that and I end up with a folder "image-shamu-n6f27h".
Now copy the following files from the new folder (e.g. "image-shamu-n6f27h") to the location where your fastboot is;
boot.img
cache.img
recovery.img
system.img
userdata.img
Navigate on the PC to the location where the fastboot binary is.
Boot the phone into fastboot by pushing and holding the volume down and power buttons
Look on the phone's screen and there should be a message "Device is unlocked. Status Code 3" confirming the bootloader is unlocked.
Double check that "fastboot devices" returns your device.
Now type "fastboot reboot-bootloader", which will power off the phone and start it again in the same place. Just double checking that you are communicating correctly with the device.
Code:
1) flash the boot image (also called the kernel):
fastboot flash boot boot.img
reboot:
fastboot reboot-bootloader
2) If you want, you can flash the radio:
fastboot flash radio radio.img
reboot:
fastboot reboot-bootloader
3) flash recovery:
fastboot flash recovery recovery.img
reboot:
fastboot reboot-bootloader
4) flash system partition:
fastboot flash system system.img
reboot:
fastboot reboot-bootloader
5) flash userdata (which will wipe the internal storage:
fastboot flash userdata userdata.img
reboot:
fastboot reboot-bootloader
6) flash cache:
fastboot flash cache cache.img
Now we are done flashing all of the partitions on a N6 so reboot to system:
fastboot reboot
If any of these fail, or don't match what I described above, post the exact errors here, preferably formatted within CODE tags. They look like: [ CODE ] [ / CODE ] without any spaces inside the brackets. The spaces are necessary to prevent the forum from executing the example as formating tags.
Posting "it doesn't work" may be funny, but it does nothing to help others help you. You must be specific as to what you were doing and what happened.
Click to expand...
Click to collapse
Thanks a lot for your assistance on this. I followed your exact instructions and it is given below.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>dir *.img
Volume in drive C is Windows8_OS
Volume Serial Number is 40E0-62B9
Directory of C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools
01-01-2009 00:00 8,686,822 boot.img
01-01-2009 00:00 6,398,184 cache.img
26-09-2017 16:53 118,279,680 radio.img
01-01-2009 00:00 14,206,186 recovery.img
01-01-2009 00:00 1,619,795,140 system.img
01-01-2009 00:00 142,201,816 userdata.img
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot devices
ZX1G525DZX fastboot
You're right. Initially it was DEVICE is UNLOCKED. Status Code 3.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
Once reboots, it says DEVICE IS LOCKED. Status Code 2. I had to long press the power key, which unlocks the DEVICE.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (8483 KB)...
OKAY [ 0.285s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.338s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.737s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.774s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13873 KB)...
OKAY [ 0.580s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.617s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (522524 KB)...
OKAY [ 18.848s]
writing 'system' 1/4...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.901s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash userdata userdata.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.037s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
vigkumar said:
Thanks a lot for your assistance on this. I followed your exact instructions and it is given below.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>dir *.img
Volume in drive C is Windows8_OS
Volume Serial Number is 40E0-62B9
Directory of C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools
01-01-2009 00:00 8,686,822 boot.img
01-01-2009 00:00 6,398,184 cache.img
26-09-2017 16:53 118,279,680 radio.img
01-01-2009 00:00 14,206,186 recovery.img
01-01-2009 00:00 1,619,795,140 system.img
01-01-2009 00:00 142,201,816 userdata.img
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot devices
ZX1G525DZX fastboot
You're right. Initially it was DEVICE is UNLOCKED. Status Code 3.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
Once reboots, it says DEVICE IS LOCKED. Status Code 2. I had to long press the power key, which unlocks the DEVICE.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (8483 KB)...
OKAY [ 0.285s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.338s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.737s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.774s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13873 KB)...
OKAY [ 0.580s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.617s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (522524 KB)...
OKAY [ 18.848s]
writing 'system' 1/4...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.901s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash userdata userdata.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.037s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Couple of questions.
You are working on a Nexus 6, right? Not a 6P or other device?
Did you reboot between each img flash? When you returned to the bootloader each time after rebooting, did you long press the power button because it still said "locked status 2"?
I have to say, this is the first I've ever heard of a reboot causing it to be locked then long pressing the power button to unlock. Either the bootloader is unlocked or it isn't.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
---------- Post added at 14:03 ---------- Previous post was at 14:00 ----------
Additional question, when you reboot using only the key combination, does it always show unlocked?
If yes to that, maybe it's back to my concern that the version of fastboot is not working well with the N6.
If you haven't, try with the minimal version you downloaded the other day.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I
vigkumar said:
Both method failed. :crying::crying:
Click to expand...
Click to collapse
1] If u can get to twrp, use microUSB flash drive and move ROMs over to flash via TWRP. Must mount OTG drive in TWRP after plugin to recognize flash drive
2) if u can get to fastboot mode and your PC recognizes your device via "fastboot device" command, try using WUG NRT tool kit to restore back to stock, then root @ND put TWRP on there, then flash custom Roms via TWRP
novice here. screwed up my 6p and got in a similar place as you are. i started adb side load in my phone and linux pc terminal, adb start-server, then adb sideload [add a space] then i dragged and dropped the factory firmware to terminal then enter. i had to try a couple of googles angler firmware before it found the the right format. saved my bacon.
Good point. If fails on Windows, Linux PC may work
Is there any way to downgrade the anroid pie to oreo
Download this to PC, this using the second link https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_ DEFAULT_CFC.xml
Using these instructions https://forum.xda-developers.com/z3-play/how-to/firmware-oficial-9-0-0-pie-instalacion-t3911995 :good:
I am considering doing this and taking the official Pie OTA, the Pie download here wont allow for updates.
Is the process to go back to Oreo 8.0 the same as the installation of Android foot?
bruney.melo said:
Is the process to go back to Oreo 8.0 the same as the installation of Android foot?
Click to expand...
Click to collapse
I dont know what Android foot is?
But I just downgraded my phone from Pie to Oreo following the instructions.
https://forum.xda-developers.com/z3...l-9-0-0-pie-instalacion-t3911995#post79284837
Just change this line to all lower case or you will get an error
"fastboot erase DDR" I got an error unless I typed it in lower case "fastboot erase ddr."
I also heeded this warning, and you should do the same unless you have a TWRP backup of the partitions.
Notes:
- These commands can be omitted to avoid having problems with the telephone signal (it is unlikely to happen but it is good to prevent)
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
want to go back to Android Oreo. I'm following the thread you sent, but I'm having trouble using adb fastboot, always the error.
Droid_Nut said:
I dont know what Android foot is?
But I just downgraded my phone from Pie to Oreo following the instructions.
https://forum.xda-developers.com/z3...l-9-0-0-pie-instalacion-t3911995#post79284837
Just change this line to all lower case or you will get an error
"fastboot erase DDR" I got an error unless I typed it in lower case "fastboot erase ddr."
I also heeded this warning, and you should do the same unless you have a TWRP backup of the partitions.
Notes:
- These commands can be omitted to avoid having problems with the telephone signal (it is unlikely to happen but it is good to prevent)
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
need to have the bootloader unlocked? here says that the device was not found.
'' (bootloader) max-download-sizer: not found
target didn't report max-download-size
sending 'partition' (37 KB)...''
bruney.melo said:
want to go back to Android Oreo. I'm following the thread you sent, but I'm having trouble using adb fastboot, always the error.
Click to expand...
Click to collapse
Did you do an initial connected with the system booted, developer options>adb debugging, and connect to your PC by typing adb devices, and getting the prompt in your phone? And when you put the phone in fastboot mode, type fastboot devices to make sure your phone is connected, it will return the serial number.
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
bruney.melo said:
need to have the bootloader unlocked? here says that the device was not found.
'' (bootloader) max-download-sizer: not found
target didn't report max-download-size
sending 'partition' (37 KB)...''
Click to expand...
Click to collapse
Not quite sure you need the bootloader unlocked, because you use a fastboot command to unlock it, before it is unlocked.
Droid_Nut said:
Did you do an initial connected with the system booted, developer options>adb debugging, and connect to your PC by typing adb devices, and getting the prompt in your phone? And when you put the phone in fastboot mode, type fastboot devices to make sure your phone is connected, it will return the serial number.
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
Not quite sure you need the bootloader unlocked, because you use a fastboot command to unlock it, before it is unlocked.
Click to expand...
Click to collapse
Yes, I did exactly everything, but this message continues.,
{
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>adb devices
List of devices attached
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>adb reboot bootloader
error: no devices/emulators found
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot devices
0050538683 fastboot
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
(bootloader) max-download-sizer: not found
target didn't report max-download-size
sending 'partition' (37 KB)...}
bruney.melo said:
Yes, I did exactly everything, but this message continues.,
{
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>adb devices
List of devices attached
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>adb reboot bootloader
error: no devices/emulators found
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot devices
0050538683 fastboot
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
(bootloader) max-download-sizer: not found
target didn't report max-download-size
sending 'partition' (37 KB)...}
Click to expand...
Click to collapse
Looks like ADB is not reporting any devices, you wont be able to do anything until you get a PC connection. Try another USB cable.
Droid_Nut said:
Looks like ADB is not reporting any devices, you wont be able to do anything until you get a PC connection. Try another USB cable.
Click to expand...
Click to collapse
I managed to make adb recognize the device, but this error happens
''C:\Users\brune\Desktop\Nova pasta>fastboot flash bootloader bootloader.img
(bootloader) max-download-sizeot: not found
target didn't report max-download-size
sending 'bootloader' (9520 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\brune\Desktop\Nova pasta>fastboot flash bluetooth BTFM.bin
(bootloader) slot-suffi: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'bluetooth' (4564 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.008s
C:\Users\brune\Desktop\Nova pasta>fastboot flash dsp dspso.bin
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'dsp' (16384 KB)...''
:crying::crying::crying::crying::crying::crying::crying:
bruney.melo said:
I managed to make adb recognize the device, but this error happens
''C:\Users\brune\Desktop\Nova pasta>fastboot flash bootloader bootloader.img
(bootloader) max-download-sizeot: not found
target didn't report max-download-size
sending 'bootloader' (9520 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\brune\Desktop\Nova pasta>fastboot flash bluetooth BTFM.bin
(bootloader) slot-suffi: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'bluetooth' (4564 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.008s
C:\Users\brune\Desktop\Nova pasta>fastboot flash dsp dspso.bin
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'dsp' (16384 KB)...''
:crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I assumed you authorized adb debugging check box on your phone, when you typed abd devices on your PC?
Is Pie still working? Not a lot of help on the Z3 section of this forum, this is getting out of my league without the phone in front of me.
Maybe link your thread to the Z2 Play section? It looks a lot more active.
Droid_Nut said:
I assumed you authorized adb debugging check box on your phone, when you typed abd devices on your PC?
Is Pie still working? Not a lot of help on the Z3 section of this forum, this is getting out of my league without the phone in front of me.
Maybe link your thread to the Z2 Play section? It looks a lot more active.
Click to expand...
Click to collapse
Yes, I authorized on the PC, all permissions have been given, the ADB Raboot Fastboot command works, the problem is running through the rom. Really JannaNsei more than doing
I don't know if Lenovo Smart Assist would allow you to flash a downgrade? It would not work with my phone, because I have an unlocked bootloader.
https://support.lenovo.com/us/en/downloads/ds101291
Droid_Nut said:
Download this to PC, this using the second link https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_ DEFAULT_CFC.xml
Using these instructions https://forum.xda-developers.com/z3-play/how-to/firmware-oficial-9-0-0-pie-instalacion-t3911995 :good:
I am considering doing this and taking the official Pie OTA, the Pie download here wont allow for updates.
Click to expand...
Click to collapse
Hello, will this downgrade method work on sprint z3 play?
I want to sim unlock it, but can't do on android 9.
Flashing ROM using fastboot MUST be done in Linux platform (Ubuntu is OK)