It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
billownz said:
It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
Click to expand...
Click to collapse
What have you been trying to flash as "bootloader" ? If you want to flash a recovery you should do
fastboot flash recovery recovery-destination-here-or-name-if-you-are-aleady-in-the-same-file.img
But I'd suggest you downloading the factory image from Google's page and doing a fresh complete install
PS don't use toolkits they are much more complicated and can mess things up
billownz said:
It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
Click to expand...
Click to collapse
I had the very same issue occur to me 18 hours out of the box on a 2013 refurb. Had to RMA to Asus. It was a hardware issue. On the repair slip they said they had to replace the board.
You might talk to them and see what a repair out of warranty would cost. There is a member here who works for Asus Customer Service, who perhaps might be able to give you some guidance. I cannot find his name at the moment, but will update with it when I do.
Update:
His name is @[email protected] and he posted here with his info: http://forum.xda-developers.com/nexus-7/help/asus-answers-t2846136
Happened the same 2me with my first nexus... I was on cm, two random reboots and that's it, couldn't flash anything, luckily i managed to relock the bootloader and erase the recovery partition (twrp)... Another user couldn't relock the bootloader so he ended up buying a motherboard on ebay
I realize this has been discussed ad nauseam and after searching through all the posts on it I am a little confused about what my options are. My Nexus 7 2013 mobile is stuck on the Google logo. Here's what I have done..
First, I tried to simply wipe the cache partition to no avail.
Second, using the WugFresh Nexus toolkit I tried to unroot and flash stock to no avail. It would get to the point of flashing I would get remote failure error messages when trying to flash the radio etc,
Basically, all I have at this point, is the Google screen and access to fastboot and it's options and the Nexus is recognized by my computer through fastboot.
What are my options now?
Should I relock the bootloader and request Google repair it?
Or should I try to flash 4.4.4 manually through fastboot without a toolkit. If so, can you refresh my memory on how to do this?
I would appreciate any help you could provide. Thanks!
Try flashing 4.4.4 manually in fastboot. There are instructions on the page where you download the firmware. Did you flash 5.0 on a LTE model?
I did not flash 5.0. It froze during usage and I restarted it and then it suddenly would not boot past the Google logo. I did nothing to it.
I downloaded the factory image for 4.4.4 and followed instructions and ran the flash-all.bat and here is what the command prompt returns:
< waiting for device >
sending 'bootloader' (3911 KB)...
OKAY [ 0.152s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.709s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'radio' (76038 KB)...
OKAY [ 3.034s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 174.608s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
Is it time to relock the bootloader and hope Google will repair it?
Hi All
I bought this phone 3 months ago, and started to use it last week. I started the phone up got the notification of Nougat update and started the upgrade this is before even signing in . In the middle of one of the updates the phone shut down, started it back up and it booted into recovery. I have tried to boot into the system about 3 times and same thing it boots into recovery. Tried to factory reset it and reboot into system bad luck.
Downloaded the firmware 6.xx and 7.xx tried to flash both of them, but I was going no where, spent few hours trying to do that till I realised that.
1- USB Debugging was disabled.
2- Bootloader was still locked.
So I am completely screwed. I have tried the Unbrick Tool and still no luck the phone has been stuck on "sending segment 1 of 'system' (2475972 KB)..." for over an hour. What is surprising it shows in the logs below that it has successfully flashed recovery.
HTML:
C:\Users\Mahmoud\Downloads\Compressed\1350\1350>flash-all.bat
Do you wish to wipe the device when flashing?(Y/N): Y
sending 'partition' (34 KB)...
OKAY [ 0.020s]
writing 'partition'...
OKAY [ 0.021s]
finished. total time: 0.049s
sending 'sbl1' (479 KB)...
OKAY [ 0.030s]
writing 'sbl1'...
OKAY [ 0.021s]
finished. total time: 0.057s
sending 'sbl1bak' (479 KB)...
OKAY [ 0.030s]
writing 'sbl1bak'...
OKAY [ 0.021s]
finished. total time: 0.059s
sending 'aboot' (701 KB)...
OKAY [ 0.030s]
writing 'aboot'...
OKAY [ 0.021s]
finished. total time: 0.055s
sending 'abootbak' (701 KB)...
OKAY [ 0.030s]
writing 'abootbak'...
OKAY [ 0.021s]
finished. total time: 0.056s
sending 'rpm' (188 KB)...
OKAY [ 0.020s]
writing 'rpm'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'rpmbak' (188 KB)...
OKAY [ 0.020s]
writing 'rpmbak'...
OKAY [ 0.021s]
finished. total time: 0.047s
sending 'tz' (561 KB)...
OKAY [ 0.030s]
writing 'tz'...
OKAY [ 0.020s]
finished. total time: 0.056s
sending 'tzbak' (561 KB)...
OKAY [ 0.030s]
writing 'tzbak'...
OKAY [ 0.020s]
finished. total time: 0.055s
sending 'hyp' (93 KB)...
OKAY [ 0.020s]
writing 'hyp'...
OKAY [ 0.021s]
finished. total time: 0.049s
sending 'hypbak' (93 KB)...
OKAY [ 0.020s]
writing 'hypbak'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'sdi' (28 KB)...
OKAY [ 0.020s]
writing 'sdi'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'pmic' (37 KB)...
OKAY [ 0.020s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'pmicbak' (37 KB)...
OKAY [ 0.020s]
writing 'pmicbak'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'hwcfg' (1 KB)...
OKAY [ 0.020s]
writing 'hwcfg'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'bluetooth' (450 KB)...
OKAY [ 0.020s]
writing 'bluetooth'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'keymaster' (148 KB)...
OKAY [ 0.020s]
writing 'keymaster'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'cmnlib' (165 KB)...
OKAY [ 0.020s]
writing 'cmnlib'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'splash' (6075 KB)...
OKAY [ 0.141s]
writing 'splash'...
OKAY [ 0.020s]
finished. total time: 0.166s
sending 'splash2' (6075 KB)...
OKAY [ 0.141s]
writing 'splash2'...
OKAY [ 0.020s]
finished. total time: 0.167s
sending 'persist' (4673 KB)...
OKAY [ 0.120s]
writing 'persist'...
OKAY [ 0.020s]
finished. total time: 0.144s
sending 'modem' (78615 KB)...
OKAY [ 1.729s]
writing 'modem'...
OKAY [ 0.013s]
finished. total time: 1.746s
sending 'cust_nv' (301 KB)...
OKAY [ 0.030s]
writing 'cust_nv'...
OKAY [ 0.021s]
finished. total time: 0.053s
sending 'systeminfo' (4 KB)...
OKAY [ 0.020s]
writing 'systeminfo'...
OKAY [ 0.021s]
finished. total time: 0.043s
sending 'KEY_INFO' (1 KB)...
OKAY [ 0.020s]
writing 'KEY_INFO'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'hidden' (9319 KB)...
OKAY [ 0.211s]
writing 'hidden'...
OKAY [ 0.020s]
finished. total time: 0.235s
sending 'sutinfo' (1 KB)...
OKAY [ 0.020s]
writing 'sutinfo'...
OKAY [ 0.021s]
finished. total time: 0.044s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
< waiting for device >
sending 'recovery' (12794 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.320s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
< waiting for device >
sending 'boot' (11746 KB)...
OKAY [ 0.281s]
writing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.306s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.011s
< waiting for device >
simu_flash:971f0dec:system
sending segment 1 of 'system' (2475972 KB)...
I tried to fool the device and downloaded twrp and named it recovery.img and placed within the same directory and again it said it was flashed as you see above, and when I tried to boot into recovery it was still the stock one.
Sadly I can't return my phone and Amazon is refusing to take it back since it was past the 30 days so I can't file an A-Z claim. I hope someone can help and giving me an idea of how to unlock the bootloader so at least I can flash stock again.
Cheers
vampire_8_7 said:
Hi All
I bought this phone 3 months ago, and started to use it last week. I started the phone up got the notification of Nougat update and started the upgrade this is before even signing in . In the middle of one of the updates the phone shut down, started it back up and it booted into recovery. I have tried to boot into the system about 3 times and same thing it boots into recovery. Tried to factory reset it and reboot into system bad luck.
Downloaded the firmware 6.xx and 7.xx tried to flash both of them, but I was going no where, spent few hours trying to do that till I realised that.
1- USB Debugging was disabled.
2- Bootloader was still locked.
So I am completely screwed. I have tried the Unbrick Tool and still no luck the phone has been stuck on "sending segment 1 of 'system' (2475972 KB)..." for over an hour. What is surprising it shows in the logs below that it has successfully flashed recovery.
C:\Users\Mahmoud\Downloads\Compressed\1350\1350>flash-all.batDo you wish to wipe the device when flashing?(Y/N): Ysending 'partition' (34 KB)...OKAY [ 0.020s]writing 'partition'...OKAY [ 0.021s]finished. total time: 0.049ssending 'sbl1' (479 KB)...OKAY [ 0.030s]writing 'sbl1'...OKAY [ 0.021s]finished. total time: 0.057ssending 'sbl1bak' (479 KB)...OKAY [ 0.030s]writing 'sbl1bak'...OKAY [ 0.021s]finished. total time: 0.059ssending 'aboot' (701 KB)...OKAY [ 0.030s]writing 'aboot'...OKAY [ 0.021s]finished. total time: 0.055ssending 'abootbak' (701 KB)...OKAY [ 0.030s]writing 'abootbak'...OKAY [ 0.021s]finished. total time: 0.056ssending 'rpm' (188 KB)...OKAY [ 0.020s]writing 'rpm'...OKAY [ 0.021s]finished. total time: 0.045ssending 'rpmbak' (188 KB)...OKAY [ 0.020s]writing 'rpmbak'...OKAY [ 0.021s]finished. total time: 0.047ssending 'tz' (561 KB)...OKAY [ 0.030s]writing 'tz'...OKAY [ 0.020s]finished. total time: 0.056ssending 'tzbak' (561 KB)...OKAY [ 0.030s]writing 'tzbak'...OKAY [ 0.020s]finished. total time: 0.055ssending 'hyp' (93 KB)...OKAY [ 0.020s]writing 'hyp'...OKAY [ 0.021s]finished. total time: 0.049ssending 'hypbak' (93 KB)...OKAY [ 0.020s]writing 'hypbak'...OKAY [ 0.021s]finished. total time: 0.045ssending 'sdi' (28 KB)...OKAY [ 0.020s]writing 'sdi'...OKAY [ 0.021s]finished. total time: 0.046ssending 'pmic' (37 KB)...OKAY [ 0.020s]writing 'pmic'...OKAY [ 0.021s]finished. total time: 0.046ssending 'pmicbak' (37 KB)...OKAY [ 0.020s]writing 'pmicbak'...OKAY [ 0.021s]finished. total time: 0.046ssending 'hwcfg' (1 KB)...OKAY [ 0.020s]writing 'hwcfg'...OKAY [ 0.021s]finished. total time: 0.045ssending 'bluetooth' (450 KB)...OKAY [ 0.020s]writing 'bluetooth'...OKAY [ 0.021s]finished. total time: 0.046ssending 'keymaster' (148 KB)...OKAY [ 0.020s]writing 'keymaster'...OKAY [ 0.021s]finished. total time: 0.046ssending 'cmnlib' (165 KB)...OKAY [ 0.020s]writing 'cmnlib'...OKAY [ 0.021s]finished. total time: 0.045ssending 'splash' (6075 KB)...OKAY [ 0.141s]writing 'splash'...OKAY [ 0.020s]finished. total time: 0.166ssending 'splash2' (6075 KB)...OKAY [ 0.141s]writing 'splash2'...OKAY [ 0.020s]finished. total time: 0.167ssending 'persist' (4673 KB)...OKAY [ 0.120s]writing 'persist'...OKAY [ 0.020s]finished. total time: 0.144ssending 'modem' (78615 KB)...OKAY [ 1.729s]writing 'modem'...OKAY [ 0.013s]finished. total time: 1.746ssending 'cust_nv' (301 KB)...OKAY [ 0.030s]writing 'cust_nv'...OKAY [ 0.021s]finished. total time: 0.053ssending 'systeminfo' (4 KB)...OKAY [ 0.020s]writing 'systeminfo'...OKAY [ 0.021s]finished. total time: 0.043ssending 'KEY_INFO' (1 KB)...OKAY [ 0.020s]writing 'KEY_INFO'...OKAY [ 0.021s]finished. total time: 0.045ssending 'hidden' (9319 KB)...OKAY [ 0.211s]writing 'hidden'...OKAY [ 0.020s]finished. total time: 0.235ssending 'sutinfo' (1 KB)...OKAY [ 0.020s]writing 'sutinfo'...OKAY [ 0.021s]finished. total time: 0.044srebooting into bootloader...OKAY [ 0.006s]finished. total time: 0.006s< waiting for device >sending 'recovery' (12794 KB)...OKAY [ 0.291s]writing 'recovery'...OKAY [ 0.020s]finished. total time: 0.320srebooting into bootloader...OKAY [ 0.003s]finished. total time: 0.003s< waiting for device >sending 'boot' (11746 KB)...OKAY [ 0.281s]writing 'boot'...OKAY [ 0.019s]finished. total time: 0.306srebooting into bootloader...OKAY [ 0.010s]finished. total time: 0.011s< waiting for device >simu_flash:971f0dec:systemsending segment 1 of 'system' (2475972 KB)...
I tried to fool the device and downloaded twrp and named it recovery.img and placed within the same directory and again it said it was flashed as you see above, and when I tried to boot into recovery it was still the stock one.
Sadly I can't return my phone and Amazon is refusing to take it back since it was past the 30 days so I can't file an A-Z claim. I hope someone can help and giving me an idea of how to unlock the bootloader so at least I can flash stock again.
Cheers
Click to expand...
Click to collapse
Have you tried using the oem unlock bootloader CMD via fast boot?
You need your bootloader unlocked to use the factory images in this first place so that's why recovery isn't sticking and I bet everything else isn't as well. Pretty stumped on this to be honest.
I recently bought a new Robin and I'm almost certain I never used stock or even booted it before unlocking my boot loader
AnierinB said:
Have you tried using the oem unlock bootloader CMD via fast boot?
You need your bootloader unlocked to use the factory images in this first place so that's why recovery isn't sticking and I bet everything else isn't as well. Pretty stumped on this to be honest.
I recently bought a new Robin and I'm almost certain I never used stock or even booted it before unlocking my boot loader
Click to expand...
Click to collapse
Hey mate yeah tried to unlock the oem and said something like bootloader is locked. I didn't get the chance to sign in once I hooked up the phone to wifi the updates started and I have proceeded, till it shut down and all fell a part. Funny enough I bought 2 Robins one for myself and one for my misses. Hers we used it on the same day it arrived and still working fine, but mine had all of this dramas.
I know it's very tough one and I am hoping that someone can help.
vampire_8_7 said:
Hey mate yeah tried to unlock the oem and said something like bootloader is locked. I didn't get the chance to sign in once I hooked up the phone to wifi the updates started and I have proceeded, till it shut down and all fell a part. Funny enough I bought 2 Robins one for myself and one for my misses. Hers we used it on the same day it arrived and still working fine, but mine had all of this dramas.
I know it's very tough one and I am hoping that someone can help.
Click to expand...
Click to collapse
Try "fastboot reboot-system (or fastboot reboot system)", if you after that load in recovery, try to see partitions via adb shell and "df" command. I have some trouble with flashing on locked bootloader, and in process - phone don't erase /system.
HeaDekBatHblu said:
Try "fastboot reboot-system (or fastboot reboot system)", if you after that load in recovery, try to see partitions via adb shell and "df" command. I have some trouble with flashing on locked bootloader, and in process - phone don't erase /system.
Click to expand...
Click to collapse
hey mate these 2 commands don't exist in the fastboot
fastboot reboot system
fastboot reboot-system
I have also tried the adb shell and it gave me "error : no devices found". I had to reboot in recovery and choose apply update via adb so I can see the listed devices.
HTML:
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe devices -l
List of devices attached
NBQGLMB660203876 sideload product:ether model:Robin device:ether
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe reboot-bootloader
error: closed
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe reboot-bootloader -i 0x2c3f
error: closed
No luck bro.
This should be recoverable.. Do you still need some help?
From what i think i understand of the circumstances:
-- You had a new phone.
-- You booted the phone, and started to download and apply the OS update over a network (for some reason.. flashing via usb would have been faster and more simple but..)
-- The update failed before it could finish, leaving you without an OS to boot into, however fastboot and stock recovery are fine
*** Everything else mentioned i believe is irrelevant.. Based on what you said happened, there shouldn't be any reason you can't recover.. It's a new phone with healthy hardware, your fastboot and recovery are intact, and It worked until the update broke the system. So if that is definitely the cause, i see no reason why this couldn't be fixed.. So just lmk if you want some additional advice before i type up a how-to for no reason, lol
soulife said:
This should be recoverable.. Do you still need some help?
From what i think i understand of the circumstances:
-- You had a new phone.
-- You booted the phone, and started to download and apply the OS update over a network (for some reason.. flashing via usb would have been faster and more simple but..)
-- The update failed before it could finish, leaving you without an OS to boot into, however fastboot and stock recovery are fine
*** Everything else mentioned i believe is irrelevant.. Based on what you said happened, there shouldn't be any reason you can't recover.. It's a new phone with healthy hardware, your fastboot and recovery are intact, and It worked until the update broke the system. So if that is definitely the cause, i see no reason why this couldn't be fixed.. So just lmk if you want some additional advice before i type up a how-to for no reason, lol
Click to expand...
Click to collapse
Hey mate so sorry for the late reply, for some reason I didn't see the notification of your reply.
Yeah fastboot and Stock recovery are working fine, but remember bootloader is still locked and the USB debugging isn't enabled. I thought it should be recoverable but I am not able to recover it and tried too many ways but they all have failed. I will appreciate some advise/help to sort this phone. Thanks
That's what I don't understand, the "bootloader is still locked" part..
You're saying that "fastboot -i 0x2c3f oem unlock" doesn't work because the "oem unlocked" setting in developer settings wasn't checked..
The robin is the first phone I owned since the extra oem bootloader security feature was introduced.. I understand now how it works and why it's there, but I didn't at the time I powered on my phone and flashed it for the first time..
When I first used the device, I powered on, skipped setup, started the system updates over wifi, and realized I was wasting time since I was gonna setup adb, fastboot, download factory images, root, unencrypt, etc.. So in the middle of the ota update I force rebooted using volume down + power, got everything setup on the laptop, and then fastboot oem unlocked and updated everything to nougat.. It wasn't until some time shortly after that I learned that it could have bricked my device, but luckily it seemed that oem unlocked is on by default.. Since I'm obviously not bricked, and also when I finally got around to enabling developer options, it was already checked without my interaction..
So that's what I'm unsure of, it's apparently already unlocked out of the box..
But fwiw, I stumbled onto an article on the razor forum about someone who bricked their phone by turning oem option off and then doing a full wipe.. One of the nextbit employees said he needed a new phone, but a user suggested a sequence of things to flash in some particular order, something like "first flash android 6, then 7" and it worked, he unbricked despite nextbit themselves telling him he was screwed..
I'll see if I can find the article again when I get some spare time. But again, from my experience, oem unlock was already on on my brand new robin.. I've never checked it once and have flashed my device several times already without issue
soulife said:
That's what I don't understand, the "bootloader is still locked" part..
You're saying that "fastboot -i 0x2c3f oem unlock" doesn't work because the "oem unlocked" setting in developer settings wasn't checked..
The robin is the first phone I owned since the extra oem bootloader security feature was introduced.. I understand now how it works and why it's there, but I didn't at the time I powered on my phone and flashed it for the first time..
When I first used the device, I powered on, skipped setup, started the system updates over wifi, and realized I was wasting time since I was gonna setup adb, fastboot, download factory images, root, unencrypt, etc.. So in the middle of the ota update I force rebooted using volume down + power, got everything setup on the laptop, and then fastboot oem unlocked and updated everything to nougat.. It wasn't until some time shortly after that I learned that it could have bricked my device, but luckily it seemed that oem unlocked is on by default.. Since I'm obviously not bricked, and also when I finally got around to enabling developer options, it was already checked without my interaction..
So that's what I'm unsure of, it's apparently already unlocked out of the box..
But fwiw, I stumbled onto an article on the razor forum about someone who bricked their phone by turning oem option off and then doing a full wipe.. One of the nextbit employees said he needed a new phone, but a user suggested a sequence of things to flash in some particular order, something like "first flash android 6, then 7" and it worked, he unbricked despite nextbit themselves telling him he was screwed..
I'll see if I can find the article again when I get some spare time. But again, from my experience, oem unlock was already on on my brand new robin.. I've never checked it once and have flashed my device several times already without issue
Click to expand...
Click to collapse
I bought 2 Robins at the time, 1 I used straight away and the other is the 1 that had the issue and I started using it like 3 months later. By default the OEM isn't toggled on I have confirmed that 100%, after the 2nd Robin got bricked. I picked up the working one and looked at it and sure enough the OEM toggle was off so I had to turn it on myself also enabled USB debugging in case this one breaks for some reason.
So yeah, basically if I tried to flash anything via fastboot it says "remote device is locked" and can't sideload anything via ADB also because USB debugging isn't enabled.
I managed to get the OTA.zip for Robin, Nougat update and half way through updating around 47% to 51% it fails, because the boot image is different off course, cause my phone still running 6.0.1, and the OTA find unmatched release keys. I think if I can find a full signed 6.0.1.zip for Robin I might be able to sideload it.
Literally I have tried everything I came across with this phone, pretty frustrating.
Thanks for your help, if you have more suggestions please let me know.
Find 6.0.1?
If you can find? It's there:
https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
And that is strange then.. My oem unlocked is checked my default and yours isn't.. Maybe my Amazon seller sold me a return lol..
Edit: ahh, I guess you meant a flashable zip? What if you pull the images, sideload them, and flash the images individually?
vampire_8_7 said:
I think if I can find a full signed 6.0.1.zip for Robin I might be able to sideload it.
Literally I have tried everything I came across with this phone, pretty frustrating.
Thanks for your help, if you have more suggestions please let me know.
Click to expand...
Click to collapse
soulife said:
If you can find? It's there:
https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
And that is strange then.. My oem unlocked is checked my default and yours isn't.. Maybe my Amazon seller sold me a return lol..
Edit: ahh, I guess you meant a flashable zip? What if you pull the images, sideload them, and flash the images individually?
Click to expand...
Click to collapse
Hey mate yeah I meant flashable.zip, and nope the images won't work via sideload. Definitely the OEM wasn't checked I got 2 Robins and both weren't toggole on.
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
matthew.bridell said:
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
Click to expand...
Click to collapse
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
CyberpodS2 said:
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
Click to expand...
Click to collapse
flash the zip? Would I just use fastboot flash image-taimen-opm1.171019.018.zip ?
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
CyberpodS2 said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
I was able to install Lineage-15.1-20180219 and boot into it. Tried to restore from that point and it now when I run flash-all it now says
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.006s
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
error: cannot load system.img from flash
Press any key to exit...
matthew.bridell said:
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
Click to expand...
Click to collapse
You need to update your platform-tools.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
just tried the zip and no luck
C:\Users\matth\Downloads>cd "platform-tools-latest-windows (2)"
C:\Users\matth\Downloads\platform-tools-latest-windows (2)>cd platform-tools
C:\Users\matth\Downloads\platform-tools-latest-windows (2)\platform-tools>flash-all
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.005s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.221s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
I do now have default Recover but don't know why it won't work.
I feel dumb. I got it to work with using a usb-a to usb-c cord. was trying to use the usb-c to usb-c cord thanks for all the help.
Hello,
I am asking here is there a way to unlock bootloader?
The situation is:
- the phone is in boot loop.
- the phone boots to download mode every time.
- cannot access to recovery mode from fastmode.
- cannot apply LG tot to refurbish in download mode. It now deads at 4% of the process.
- and the last, I didn't enable OEM unlocking when the phone was still functioning.
Adb, fastboot, I tried all the commands that I know so far, but no help.
I know that I have to enable OEM unlocking to be able to unlock bootloader. But again, I cannot boot in to do it.
So just hope that some experts might know a way.
You don't have a possibility to unlock it!
The only way is by settings from working phone.
S C:\Android\platform-tools> .\fastboot.exe devices
0171046759b8474f fastboot
PS C:\Android\platform-tools> fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ 0.020s]
finished. total time: 0.021s
PS C:\Android\platform-tools> fastboot.exe flashing unlock
...
OKAY [ 9.244s]
finished. total time: 9.247s
PS C:\Android\platform-tools> fastboot.exe flashing unlock
...
FAILED (remote: Already unlocked)
finished. total time: 0.008s
PS C:\Android\platform-tools> fastboot flash boot boot-fixed.img
target reported max download size of 536870912 bytes
sending 'boot' (11797 KB)...
OKAY [ 0.321s]
writing 'boot'...
OKAY [ 0.137s]
finished. total time: 0.461s
PS C:\Android\platform-tools> fastboot flash recovery recovery-fixed.img
target reported max download size of 536870912 bytes
sending 'recovery' (17437 KB)...
OKAY [ 0.459s]
writing 'recovery'...
OKAY [ 0.209s]
finished. total time: 0.671s
PS C:\Android\platform-tools>
Sigh,
So no more hope.
Thank you ^_^
Try the battery discharge trick described by sd_cb on the page Fix-a-Brick: Fighting the Nexus 5X Bootloop:
"One trick I learned for my bootlooped 5X is that first you let the phone completely drain of battery (boot into recovery and let it sit). Then, plug in the phone and boot up. I would get ~1 minute in the phone before it would reset. What did this do for me? It allowed me to recover my 2 factor codes that I was stupid enough not to print or save to begin with. Lesson learned"