[Q] fastboot flash doesn't work - Nexus One Q&A, Help & Troubleshooting

I am trying to burn stock ROM images on my Nexus One. I am trying to follow instructions in this tutorial http://forum.xda-developers.com/showthread.php?t=614850 but can't get fastboot to flash my ROM with the images nor erase the userdata partition.
When trying
-> fastboot erase userdata
I get "FAILED (remote: not allowed)" message and when trying
-> fastboot flash userimage.img
I get "sending 'userdata' (837 KB)..." but nothing happens even after 10 minutes... This is the same when trying to flash system and boot partition as well.
I can see my device and reboot it using
-> fastboot devices
-> fastboot reboot-bootloader
My HBOOT version is 0.33.0012 and I have this S-ON (can't quite figure out what this means)...
Any ideas?

When in the bootloader does it say HBOOT below the green text or FASTBOOT? You will first need to navigate to the fastboot entry (I think that's what it's called) and press the power button. Your commands should then work.

Hollow.Droid said:
When in the bootloader does it say HBOOT below the green text or FASTBOOT? You will first need to navigate to the fastboot entry (I think that's what it's called) and press the power button. Your commands should then work.
Click to expand...
Click to collapse
It says FASTBOOT USB. I can see the device and do a reboot using the fastboot tool in my PC - only the erase and flash commands don't seem to work.

smichak said:
It says FASTBOOT USB. I can see the device and do a reboot using the fastboot tool in my PC - only the erase and flash commands don't seem to work.
Click to expand...
Click to collapse
Hmmm that's weird, I only got those errors when it said HBOOT. An alternative is to flash the phone using PASSIMG.zip. It will wipe the partitions you are attempting to; userdata, system, boot etc using a completely stock rom and is done via the fastboot menu.
Edit: This is assuming you have an unlocked bootloader?

Did you run 'fastboot oem unlock' first?

Rusty! said:
Did you run 'fastboot oem unlock' first?
Click to expand...
Click to collapse
I am pretty sure my phone is unlocked as I see this open lock icon whenever I reboot it.

Hollow.Droid said:
Hmmm that's weird, I only got those errors when it said HBOOT. An alternative is to flash the phone using PASSIMG.zip. It will wipe the partitions you are attempting to; userdata, system, boot etc using a completely stock rom and is done via the fastboot menu.
Edit: This is assuming you have an unlocked bootloader?
Click to expand...
Click to collapse
Is there a tutorial or something on how to do this (the PASSIMG.zip thing) ? I don't wanna mess things up...

smichak said:
Is there a tutorial or something on how to do this (the PASSIMG.zip thing) ? I don't wanna mess things up...
Click to expand...
Click to collapse
There was but I can't put my finger on it at the moment. However I used this exact method a couple of days ago so it's still fresh:
1) Download FRG33 image format from here. Versions above this as far as I know cannot use the PASSIMG.zip method.
2) Rename to PASSIMG.zip and place in the root of the sd card
3) Reboot/boot to bootloader
4) At this point the phone will recognise the zip file and check its contents.
5) When prompted press the volume button to confirm.
This will return you to stock (Minus the recovery but from the sounds of it you don't have a custom recovery image).

You have to extract the FRG33 file and then rename the new file passimg.zip

OK thanks - the PASSIMG.zip thing did the trick. Now I'm running FRG33 stock. Any tips on how I get from here as quickly as possible to Gingerbread?

smichak said:
OK thanks - the PASSIMG.zip thing did the trick. Now I'm running FRG33 stock. Any tips on how I get from here as quickly as possible to Gingerbread?
Click to expand...
Click to collapse
Using fastboot, flash the custom recovery of your choice. Using that recovery, flash the custom GB ROM of your choice.

Related

Please Help "Brick" with Cyanogen's newest upate

My first post but I've been lurking for years. Pretty good with search, etc.
If anyone could help I would really appreciate it. I've been working on this for 12 hours!
I updated to Cyanogen 4.1.999
I successfully installed the new radio and fastboot confirms 2.22.19.261
Here's where I made the mistake in the following directions:
I have CMRecovery Image 1.4
-Go to http://developer.htc.com/adp.html
-DL the 1.6 "recovery image" the file name is - signed-dream_devphone_userdebug-ota-14721.zip
-Then DL CyanogenMod-4.1.99
http://n0rp.chemlab.org/android/expe....99-signed.zip
-put them both on your SD card
-Boot up into CM recovery image 1.4 by rebooting and holding the home button, do a wipe.
-update using any zip to that "recovery image" (signed-dream_devphone_userdebug-ota-14721.zip)
(it should auto reboot install radio then reboot again and load back up to the CMrecovery img screen)
I mistakenly rebooted normally instead of applying the update in the next step. This is when the black screen began.
-Then update any zip usig CyanogenMod-4.1.99 (update-cm-4.1.99-signed.zip)
-Then power on the phone
I am stuck at the black screen of death.
I can fastboot and I've fastbooted the pimp recovery and still can't access recovery. Just get the triangle.
So, during update after new radio I rebooted normally instead of updating with the final build update got a black screen and have no recovery.
I've tried fastboot flash recovery and fastboot update.
fastboot flash recovery is succesful
fastboot update or fastboot flashall give me the "archive does not contain android-info.text and android-product.text" errors.
Any ideas would be greatly appreciated.
this should be posted in Q/A not development.
cingall said:
this should be posted in Q/A not development.
Click to expand...
Click to collapse
Sorry!
Mod please move. Thanks!
if you have access to fastboot, do a fastboot flash everything... from radio, system, and what not (forgetting something)
if that doesn't work... do a fastboot of the radio and boot and system, do everything.
basically do a fastboot of the normal dev 1.6 system....
its on htc's website.... gl dude
theomajigga said:
if you have access to fastboot, do a fastboot flash everything... from radio, system, and what not (forgetting something)
if that doesn't work... do a fastboot of the radio and boot and system, do everything.
basically do a fastboot of the normal dev 1.6 system....
its on htc's website.... gl dude
Click to expand...
Click to collapse
any ideas on the commands to flash them as flashall? HTC's site has them as separate files so I can only flash the "recovery" file.
I'm sorry to be somewhat of a noob with the actual codes. Could you be more specifc with which files to flash with which commands?
TIA!
Using the HTC website 1.6 "recovery" with fastboot update I get the following:
Error: update package has no android-info.txt or android-product.txt
I can't figure out how to flash the radio or system files in any other way than update in fastboot.
Did you erase the recovery? When this happened to me, just installing CM 1.4 from fastboot did not work, I had to erase the recovery then install. Hope this helps.
Also remove your SD card while booting, as prior stuff in your ext3 partition can cause black screens during boot. If that fixes it, you need to reformat your ext3.
The triangle you see is the standard recovery, to access it you need to do alt-L?or alt-x cant remember. To fix you need to flash cm-recovery to do this reboot into the boot loader (power + camera) plug in usb and hit the back button you should see "fastboot" then run
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
seehttp://forum.xda-developers.com/showthread.php?t=523558
then install rom as normal
okay this happened to me as well. I just made sure that I wiped, then started allover again. i had to do it a couple of times but it worked. just make sure that you still have the files on your SD card.
Good Luck!!!!
brnbock said:
Did you erase the recovery? When this happened to me, just installing CM 1.4 from fastboot did not work, I had to erase the recovery then install. Hope this helps.
Click to expand...
Click to collapse
You are a STAR!! Thank you, thank you, thank you!! I knew it was something stupid!
Back at the recovery console! woot!!!
Mods please close this thread!
Please Help "Brick" with Cyanogen's newest upate
Do you still need help bricking your phone???
took 30 min to post a re.. sorry i was late
fastboot erase recovery
fastboot flash recovery *name of recovery*
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
That should fix it.
ugh, now I am stuck at the g1 screen after a reboot of a successful update.
reformatted sd and all probs are solved!
mghtyred said:
Please Help "Brick" with Cyanogen's newest upate
Do you still need help bricking your phone???
Click to expand...
Click to collapse
Hi mghtyred (of tmobile forums) welcome to XDA

Flashing 5.0.1

I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
SoCoCapricorn said:
I downloaded the flashable zip from https://www.androidfilehost.com/?fid=95851846488293411
I use WugToolKit with TWRP, Unlocked and Decrypted. Stock ROM
I'm confused as to how I should flash this, I've read I should just click flash zip in the toolkit and let it finish and done. Also that I could download the file to my phone and use TWRP to flash straight to the phone. Some say backup and some say don't. Also some threads say I need to flash back to factory image, tho this flashable zip should be a factory image of 5.0.1.
Any help will be appreciated. Thank you.
Sent from my Nexus 6
Click to expand...
Click to collapse
Apparently the new update OTA or zip will update blocks instead of files so from my understanding, even the slightest change from stock will cause this ZIP to fail when flashing. I'm rooted, decrypted, and changed mixer_paths.xml and as expected the flash failed in TWRP and adb sideload so I'm backing up via Titanium and flashing the 5.0.1 stock. I'll decrypt/root/restore after the flash.
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
mzimand said:
So if I am stock but rooted I cannot sideload the OTA?
I keep getting status 7 error when trying to sideload with ADB using the update OTA.
It actual unzips and installs about 50% and then I get the Status 7 Error
Click to expand...
Click to collapse
Rooting causes a change to the system partition, so no, you can't sideload the OTA anymore. (not since Lollipop)
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Worked like a CHAMP!!
:highfive:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Are you using nexus toolkit by wug?
Sent from my Nexus 6
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, just used the steps I listed.
SoCoCapricorn said:
Are you using nexus toolkit by wug?
Sent from my Nexus 6
Click to expand...
Click to collapse
No, he used fastboot. Be wary of toolkits. They can do damage that a novice wont be able to fix.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Jeezus! perfect!
Thats similar to what I did.
Only thing to do if you are already decrypted is to download this boot file, rename it to boot.img and flash it instead of the one included in the google zip package.
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
dunjamon said:
I had to manually flash each file separately. For some reason when the flash.bat file was running it kept reporting that the system.img file was too big. Not had that before.
Click to expand...
Click to collapse
yeah - since 5.0, the flash-all.bat isn't working for a lot of users.
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
What about the cache.img? do we not flash the cache?
mzimand said:
What about the cache.img? do we not flash the cache?
Click to expand...
Click to collapse
From what I understand, if you flash cache.img, you will go back to stock and lose all of your settings.
Awesome man, worked perfect, you sir rock!
Great!!!!
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
It works like a champ! THX man :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Excellent, works perfectly as described. Thanks
The only thing that I'd add, to avoid any confusion, is that the factory image can be downloaded from:
https://developers.google.com/android/nexus/images
Thanks again, stevetrooper :good:
stevetrooper said:
Here are the steps I took to flash the factory image and not lose my settings:
Flash bootloader and radio:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
I then unzipped this file: image-shamu-lrx22c.zip
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
After the phone restarted I then used CF-Auto-Root to re-root my phone. I did not lose any of my settings or installed apps. HTH...
Click to expand...
Click to collapse
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Having an issue while flashing system.img file. I flashed radio, and flashed system.img then flashed cf-auto-root. On first start up I was having issues with my radio. LTE was not connecting to T Mobile. So I Nandroid back to stock. Then of course I noticed this didnt change my radio back to stock. Starting everything over, I reflashed radio, reboot bootloader, Flash system.img, reboot bootloader, then fash autoroot. Restart device. Radio was flashed and I had root, but stuck on 5.0 Tried to reflash system.img and I am getting error. "access denied" when flashing. I have read this is an issue with mounting the drive, I have even tried to do this in fast boot but I am coming up with nothing. Any help on this will be greatly appreciated.
theblizzard2010 said:
Curious as to why so many steps?
All i did was flash the radio and system images. Went to 5.0.1 just fine, all settings/data retained.
Didn't flash bootloader, kept unlocked during process, only had to re-root.
Click to expand...
Click to collapse

[Q] Mismatched partition size (recovery) when flashing stock 5.0.1 recovery

I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.
Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.
Evo_Shift said:
Try flashing the recovery again. I think if I was you I would also fastboot -w to format the userdata and cache since you already did a factory reset or use google's images by using "fastboot flash userdata userdata.img", "fastboot erase cache" and then "fastboot flash cache cache.img".
Also, check the md5 of the image you downloaded to make sure it was not corrupt.
Click to expand...
Click to collapse
I used fastboot -w to format the userdata/cache. And I also tried the three fastboot commands you listed. They all seem to work, but the reflashing of the recovery still throws the same error.
MD5 checksum of the whole zip is the same. I re-extracted the recovery.img file just to be sure and it still throws the same error.
Kramit said:
when I try to get back into recovery, the phone sits at the android with the red triangle and !.
Click to expand...
Click to collapse
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.
rootSU said:
Thats normal though isn't it? With Stock recovery you have to press Volume up and power to get into the recovery menu from that screen
Click to expand...
Click to collapse
yes, thats norml
cmh714 said:
yes, thats norml
Click to expand...
Click to collapse
Hmm. And if it doesn't work?
Kramit said:
I am trying to back out everything I've done to the phone and start fresh with 5.1. I had rooted, decrypted, and installed TWRP. To undo this, I did a factory reset, downloaded the shamu-lrx22c factory image from google, and used adb/fastboot to put it all back the way I found it. These are the commands I used :
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
It appeared to all work. Now when I try to get back into recovery, the phone sits at the android with the red triangle and !. The bootloader logs state "Mismatched partition size (recovery)."
Did I do a bad thing somewhere along the way? Thanks in advance.
Click to expand...
Click to collapse
I have the same problem here but maybe i have found a solution for it:
what i did was i left the 5.1 bootloader.img and took all the other stuff from a 5.0 factory image such as: radio.img, system.img..... fastbooted everything and i was with a 5.0 LP stock out of the box, then i have rooted it, installed twrp with f2fs support and voila i'm now good to go
hope this will help you out
Kramit said:
Sadly, that doesn't do anything. Pressed repeatedly, held down for a while, nothing. up until the point where it reboots from the power button being held long enough.
Click to expand...
Click to collapse
When you see the android with the red triangle and !, you need to hold the power button, and while you are holding it down, press volume up. Pushing them both together, or one after the other, or holding them down together or whatever else won't work.
Sent from my Nexus 6 using Tapatalk

Did I really just brick a NEXUS?!?!

Think I may be officially bricked ... tried to sideload the OTA this morning with no luck (looped at Google splash screen). So I flashed the 5.0.1 images and went about my day. Came home and flashed the 5.1 images and looped at the Google splash again ... continued to tinker and play. Long story short, in my idiocy I oem locked. Now I can't flash any .img files cause I am locked, can't unlock because I can't boot into Android and uncheck the stupid box in dev options and trying to sideload the ota .zip again yields: "/dev/block/platform/msm_sdcc.1/by-name/system has been removed R/W; reflash device to reenable OTA updates E:Error in sideload/package.zip (Status 7)" ...
At this point I think I am screwed!! Any suggestions would be GREATLY appreciated!
Can you not get into fastboot and try to OEM unlock that way?
Xaikar said:
Can you not get into fastboot and try to OEM unlock that way?
Click to expand...
Click to collapse
I can get into fastboot but get this when I try to unlock
C:\Android\sdk\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.000s
C:\Android\sdk\platform-tools>​
And of course I cannot check that because I cannot boot into Android
So it currently says device locked?
Xaikar said:
So it currently says device locked?
Click to expand...
Click to collapse
10-4
I can get into stock recovery, but I don't know of anything to flash with the stock recovery and adb sideloading 5.1 isn't working
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
There's a thread about this over at the Nexus 9 help forum. Might want to check there.
Xaikar said:
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Click to expand...
Click to collapse
Can't flash the images while locked, thanks though
ChristianJay said:
There's a thread about this over at the Nexus 9 help forum. Might want to check there.
Click to expand...
Click to collapse
Ah, thanks! Any idea which section?
Edit: Found it!
YankInDaSouth said:
Ah, thanks! Any idea which section?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312
Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img
WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.
ajjames01 said:
Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img
Click to expand...
Click to collapse
Custom recovery isn't currently on the device ...
Dusty Rhodes said:
WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.
Click to expand...
Click to collapse
Tried that too ... but the .img's cannot be flashed while locked, keeps failing
If you have TWRP on the device can you adb push a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.
ajjames01 said:
If you have TWRP on the device can you a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.
Click to expand...
Click to collapse
I don't have TWRP, sorry that was a typo. It's stock recovery as I was trying to go fully stock 5.1 ...
@YankInDaSouth
Did you try booting twrp and not flashing it and go from there?
Fastboot boot recovery twrp.img
when Google decided to add the "OEM Lock" checkbox they should have committed to every Nexus device also having SD card capability, not only for the convenience that SD cards bring but also to be able to load the images that way in the event of a catastrophe.
But I guess forcing everyone into buying cloud storage is the new modus operandi.
Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot
efrant said:
Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot
Click to expand...
Click to collapse
Still get the message about checking the box in dev options ...
Not sleeping tonight huh bro? I know the feeling when this **** happens, it sucks. I think someone will come up with a work around, a lot of brains around here.
Sent from my Nexus 9 using XDA Free mobile app

Device is corrupt. It can't be trusted and will not boot

Can't even fastboot flash boot recovery system...and thats all folks...waste of money.
Failed attempt to unlock the bootloader and instal TWRP ?
Hi guys, visit this link. We had similar problems and we could solved that.
Read all and you would get the solution
https://forum.xda-developers.com/red-magic-3/help/stuck-fastboot-mode-t3937527/page9
roadworker said:
Failed attempt to unlock the bootloader and instal TWRP ?
Click to expand...
Click to collapse
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.
Just flash the ROM again..It will be back lm
mhex said:
Just flash the ROM again..It will be back lm
Click to expand...
Click to collapse
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked
SuperDroidMe said:
Trying to NA Global original rom, problem is no recovery at all....I can only flash within fastboot.....which is not a problem, but phone is not taking it flashing all images individually and modem. And I know it's flashing cause fastboot is saying okay and bootloader showing unlocked
Click to expand...
Click to collapse
Every time you restart back to the bootloader you need to do: "fastboot oem nubia_unlock NUBIA_NX629J" first
SuperDroidMe said:
No I installed Chinese v2.27.... Well it's absolute mess like I never seen Android before. Then attempted to flash global again, problems to the point of corruption. I have fastboot flashed all key elements of working Android phone multiple times. Can only get to fastboot after boot screen that I have to do manually. Recovery system is toast.... Guess it's back to Poco F1.... Learned my lesson from junk.
Click to expand...
Click to collapse
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.
xphyle1971 said:
So YOU mess up your phone by trying to flash sh!t and you blame the MANUFACTURER? Yeah ok. Lmao. Enjoy the new paperweight that YOU CREATED.
Click to expand...
Click to collapse
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.
SuperDroidMe said:
LMAO if you can't go from stock global to stock Chinese and reverse from the manufacturer with their recovery, you haven't got a prayer for custom roms or mods.
Click to expand...
Click to collapse
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot
mswl04 said:
if you stuck in the Device is corrupt. It can't be trusted and will not boot and you are in the Chinese or global rom then flash the stock boot image via adb. well I am using a Chinese v2.27 rom with rooted +gapps and then realized that most of the google apps wont work correctly because of the unlocked bootloader. I tried to lock the bootloader via adb then the message "Device is corrupt. It can't be trusted and will not boot" show up. so I try to use adb to flash the stock boot image then it work. first place the stock boot image to the "Minimal ADB and Fastboot" folder which located in the local drive under program file(x86) then run the command
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.
SuperDroidMe said:
Bud I put so much effort in last 13 hours to no avail....fastboot erased all partitions, reformatted, reflashed to no avail. Right now it just boots loops on Chinese 2.27 boot splash, I do have Chinese recovery though, but the same otg adapter and pen drive that works on 5 different devices, this damn phone won't read it so even that is out of the question. I wipe my hands clean of it, some things just best to put a bullet through it.
Click to expand...
Click to collapse
btw did you rooted the phone?
mswl04 said:
btw did you rooted the phone?
Click to expand...
Click to collapse
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.
SuperDroidMe said:
No BS, all I did was flash CN 2.27 over NA Global, after a look at the mess it was I proceeded to flash NA Global back.....no TWRP No Root with SuperSU or Magisk. But in fastboot it does say Root=1, so I guess the CN 2.27 rooted it by default cause I sure as hell didn't. One thing that is bothering me while in fastboot unlock bootloader I can't turn Secure Boot off which I believe is why it won't boot system.
Click to expand...
Click to collapse
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick
mswl04 said:
don't give up I know how do you feel did you download this update from the official red magic website http://ui.nubia.cn/rom/detail/62 after you download the update and it will be in a zip file extract the boot image. then try to follow the root guild https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 in the website download the adb and then run the command which I reply earlier
seem to me it is like a soft brick
Click to expand...
Click to collapse
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?
SuperDroidMe said:
I got CN version 2.27 images, am I supposed to be using one of the other versions off the official site?
Click to expand...
Click to collapse
all you need to do is to fix the corrupt image so later once you finish the first step of booting to the phone then you can flash to global rom. if you have the cn version 2.27 boot.img then you can download the adb and use the command to fix the phone
Shouldn't have messed with something that wasn't broken. Now you have a nice brick to use as a paperweight. Hope you get it fixed tho. Good luck.
Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.
SuperDroidMe said:
Solved Instructions:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot bootloader
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot flash dsp dspso.bin
fastboot oem nubia_lock NUBIA_NX629J
fastboot reboot
*****as soon as boot screen appears hold volume + button, now in recovery...navigate to wipe data and then wipe cache....then plug in otg usb pen drive (formatted FAT32) with Rom package .zip....navigate to update otg in recovery select it let it do its thing and walla your phone is fixed.
*****if you ever go from CN rom to Global rom you must Wipe Data and Cache through recovery, it is not enough to do it in fastboot and your device will remain soft bricked.
Click to expand...
Click to collapse
Congrat you finally fix it
Hows your phone?..Did it work.

Categories

Resources