Related
UPDATE: Still no solution found - new Ideas very welcome.
Hi there,
I'm at the end of my wits with my HOX which is with a german o2 branding. After getting stuck in bootscreen after athe OTA-Update from 1.26.207.2 to 1.28.207.9 - which failed for some reasons. I tried to install different Custom-Roms, none of which would boot beyond the first HTC-Screen.
The latest one I tried was Cyanogenmod, that did boot fully but I got constant "andoidupi crashed" messages, so I tried to reflash it.
After that things got weird, because right now I can't really do anything anymore. If I try to relock it via "Fastboot oem lock" it just reboots and it boots straight into CWM 5.8.3.1 but when I get back to bootloader its still "**** UNLOCKED ****"
I can flash boot.imgs via fastboot flash... but even so its says at the command prompt that it was successful flashed, it really isnt. No matter what - at reboot I will boot into CWM.
It is like working on a virtual machine - the HOX gives all the right responses, but noting I try to flash is permanent.
I can't relock, I can't flash new recoverys, can't flash new boot.img and everything I push onto the SDCARD via adb is gone after reboot. If I delete a file that is actually on the SDCARD it will be back after reboot, like it was never really deleted.
I already checked my drivers, switched off Antivir, tried it on a different PC, reinstalled the drivers etc etc.
My HOX is from German o2
I've got HBOOT 0.94.0000 and Radio 1.1204.90.13
If anyone has any suggestions besides "You have to fastboot flash recovery/boot..." and "Don't forget to erase cache after every flash" I'd be very thankfull
Best regards,
Thad
did you try to re-download your fastboot ?
and did you navigate on CMD to the right place where your fastboot folder is stored ?
You need to flash the stock recovery before you relock your bootloader.
Flash stock recovery
Relock bootloader
Install ruu
Hope this helped
EDIT: Just read your post again and you said you've tried flashing recoveries, sorry, its late here
Sent from my HTC One X using xda premium
i made a compilation of threads about this matter, it might help you. check it out..
http://forum.xda-developers.com/show....php?t=1692681
Thanks for all suggestions on the topic
@muamers
I redownloaded fastboot multiple times, but its all the same, sadly The problem is: It seems to work. I get all the right replies on the command prompt, but after rebooting nothing is flashed.
@mikey0105
The link goes to a 404 page - could you post it again?
Thank you
tadeausz said:
Thanks for all suggestions on the topic
@mikey0105
The link goes to a 404 page - could you post it again?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1692681
Thank you Gibeon & mikey0105
I retried all the steps there, but still no change.
The problem still is the same. This is what I get in response:
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.044s]
finished. total time: 0.045s
>fastboot flash boot boot.img
sending 'boot' (4156 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.470s]
finished. total time: 1.008s
>fastboot erase cache
erasing 'cache'...
OKAY [ 0.034s]
finished. total time: 0.034s
>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru_fixedadbusb.img
sending 'recovery' (5760 KB)...
OKAY [ 0.829s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.548s]
finished. total time: 1.377s
So everything should've worked out great. But not so, because in reality he really hasn't flashed anything to the HOX permanently. When I reboot to recovery I still have the OLD CWM without fixes. The boot.img isn't flashed either.
As I said: It's like working on a virtual machine, where nothing really has any effects, it's a if all the fastboot commands only affect the RAM but are not really flashed to Memory.
And I still can't relock, still can't reboot-bootloader from Bootloader.
Any other ideas are welcome...
Greetings,
Thad
Bump.
Nobody any more ideas?
Bump. Still no solution after many month
try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager
robchongke said:
try to flash the latest CWM recovery. http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery
tadeausz said:
I'd like to - but as I said - it won't flash anything. I get the right responses but after a reboot it's back to the old Recovery
Click to expand...
Click to collapse
are you doing
fastboot flash recovery recovery.img
Or
fastboot boot recovery.img
I'm not sure the second one works, but if it did, it would do what you describe. So do the first.
help
I'm running ICJ ROM AOKP. last time I flashed this rom and flashed the gapps too,
Now I want to install a new package of gapps, SO, do I need to wipe data, cache, dalvic cache to install the gapps ???
Note that I'm going to install ONLY the gapps...
THANKS
aimen7 said:
i'm running icj rom aokp. Last time i flashed this rom and flashed the gapps too,
now i want to install a new package of gapps, so, do i need to wipe data, cache, dalvic cache to install the gapps ???
Note that i'm going to install only the gapps...
Thanks
Click to expand...
Click to collapse
That's the third time I've read this question from you.
STOP POSTING IT NOW!
BenPope said:
That's the third time I've read this question from you.
STOP POSTING IT NOW!
Click to expand...
Click to collapse
sorry, I'm CONFUSED about that
Aimen7 said:
sorry, I'm CONFUSED about that
Click to expand...
Click to collapse
Make 1 new thread or search....don't go posting it in every Q&A thread !
That is confusing ! :thumbdown:
Hey,
I have here a Galaxy Nexus Device, bought from ebay.
Nothing will really work right now. I try to flash the original google factory image.
Loaded everything, have fastboot access.
Followed the steps to flash the files over fastboot.
On Step: fastboot -w update factory-image-name nothing happens
The device says "flash:system" and the promt says writing "system" - but thats for about 20 Minutes. Tried these a lots of times.
Downloaded the toolkit here on xda. Flashed the stock-recovery. Tried that again. Nothing happens.
I'm don't know, what I'm doing wrong.
Something is wrong with the device.
There is a rom on the device. Everytime I safe an e.g. image or data on the sd and restart the device, the file is lost. I can't even restore factory setting via rom. The device boot and then appears a android man with an red triangle. After 2 minutes the device restart itself and nothing happens. Same rom as before.
The other thing thats strange. Tried to flash the new JB google factory reset. In the steps, where i should update and flash a new bootloader - the one with the C03 on the end, everything went fine. After I reboot the bootloader - the old bootloader is sill on the device - A03....
Dont know whats going on there.
Would be awesome if someone could help me.
Shizophren said:
Hey,
I have here a Galaxy Nexus Device, bought from ebay.
Nothing will really work right now. I try to flash the original google factory image.
Loaded everything, have fastboot access.
Followed the steps to flash the files over fastboot.
On Step: fastboot -w update factory-image-name nothing happens
The device says "flash:system" and the promt says writing "system" - but thats for about 20 Minutes. Tried these a lots of times.
Downloaded the toolkit here on xda. Flashed the stock-recovery. Tried that again. Nothing happens.
I'm don't know, what I'm doing wrong.
Something is wrong with the device.
There is a rom on the device. Everytime I safe an e.g. image or data on the sd and restart the device, the file is lost. I can't even restore factory setting via rom. The device boot and then appears a android man with an red triangle. After 2 minutes the device restart itself and nothing happens. Same rom as before.
The other thing thats strange. Tried to flash the new JB google factory reset. In the steps, where i should update and flash a new bootloader - the one with the C03 on the end, everything went fine. After I reboot the bootloader - the old bootloader is sill on the device - A03....
Dont know whats going on there.
Would be awesome if someone could help me.
Click to expand...
Click to collapse
I flash a lot of time on this type of device so far doesn't give a problem to me. Maybe something wrong with your device or maybe you can try to flash it via GNex toolkit and download the .tgz file from program first maybe you will have a luck.
sounds a little like bad flash ROM but I'd leave that to the pros to diagnose... mabye there was a cause why somebody put it on ebay ^^
Instead of flashing the factory image zip you could extract the system.img, boot.img, and data.img from that zip and flash them one by one.
Follow this guide: http://forum.xda-developers.com/showthread.php?p=25477039
Sent from my Nexus 7 using xda premium
@compuzones thanks for your answer. I tried this already. But no success.
@Hannes The Hun you could be right, but whats could cause the problem? I have no clue
@El Daddy I'll give it a try.
Edit:
So this is what happend. Would appreciate some expert thoughts on it.
I extracted the factory image and tried to flash the seperate files manually.
First the bootloader:
In fastboot mode my device shows me, that theese bootloader is on it:
PRIMALA03
So i pushed the newer one on it - fastboot flash bootloader bootloader-maguro-primelc03.img
sending bootloader - OKAY
writing bootloader - OKAY
the operation seems to work. But, when I'm restart-bootloader again, I have still PRIMELA03 as my bootloader.
Ok, I thought that unimportant. So tried to go on with the system.
fastboot flash system system.img
sending system OKAY
writing system..............
So here we go. It writes the system for over 20 minutes. Don't know why it exactly happens.
This happens wether I try to flash a factory image with the toolkit here from xda, or the google way or just this way.
Whats strange too.
Wanted to flash via CMW a custom rom. Just to trie it, if this woul work.
I flash CWM via the toolkit. The operation went fine. When I trie to boot in recovery, I get still the little Android with the red triangle and nothing happens.
Althouh the rom, that I put on the sd is gone after restart! Nothing there. Everythings wipe the whole time I start the device.
Edit2: After 25 Minutes it says system write ok. Here what i did:
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash system system.img
sending 'system' (396675 KB)... OKAY
writing 'system'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash userdata userdata.img
sending 'userdata' (137554 KB)... OKAY
writing 'userdata'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash boot boot.img
sending 'boot' (4366 KB)... OKAY
writing 'boot'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fsatboot flash recovery recovery.img
Der Befehl "fsatboot" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
C:\Users\GChroner\Downloads\GN\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (4708 KB)... OKAY
writing 'recovery'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot erase cache
erasing 'cache'... OKAY
C:\Users\GChroner\Downloads\GN\fastboot>fastboot reboot
rebooting...
Click to expand...
Click to collapse
But still the old rom on my device ^^ can't figure out whats all about. The device saves absolutely nothing.
Is there a possibility to check the file system or sdcard for errors or something?
Even factory reset over the android option doesn't work. It reboots and then appears the Android with the red triangle again. After some time, the rom boots again^^
Hi there,
I have just tried to root my HTC one, and I am now stuck in the boot loader screen and it is showing *Tampered* at the top.
Can someone please advise me, or point in the direction of what I need to do now?
Thanks.
If it says tampered it should say unlocked right below it.... go to this site and follow the instructions to get full root. http://forum.xda-developers.com/showthread.php?t=2699065
jeanxx said:
If it says tampered it should say unlocked right below it.... go to this site and follow the instructions to get full root. http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
I should have mentioned that I only have a Mac.....
Yes it does say unlocked underneath it...
Suggestions?
millhhaus said:
I should have mentioned that I only have a Mac.....
Yes it does say unlocked underneath it...
Suggestions?
Click to expand...
Click to collapse
Once you have unlocked your bootloader then it will show you tampered.
Download a custom recovery (I prefer TWRP) and flash it via fastboot.
Then download @Chainfire Supersu flashable zip from his site and flash it in recovery.
You have rooted your phone.
Ater placing my device into fastboot mode, I have tried flashing my downloaded TWRP file to my HTC One in Terminal using these instructions:
Now let's flash your downloaded TWRP file to your HTC One. Type one of the following commands into your terminal window, depending on which file you downloaded above.
For the International editions, type:
fastboot flash recovery Desktop/openrecovery-twrp-2.7.0.2-m8.img
However I get the following error:
command not found
any help would be most appreciated.
Did you setup your mac to use adb / fastboot commands?
lazydesi said:
Did you setup your mac to use adb / fastboot commabds?
Click to expand...
Click to collapse
I feel like a total N00b at the moment. LOL.
No. How do I do that?
try this
http://forum.xda-developers.com/showthread.php?t=2638673
Thanks for that information.
Now, when I am trying and to flash TWRP via fastboot I am getting this error message:
ERROR: Unable to create a plug-in (e00002c7)
< waiting for device >
ERROR: Unable to create a plug-in (e00002c7)
millhhaus said:
Thanks for that information.
Now, when I am trying and to flash TWRP via fastboot I am getting this error message:
ERROR: Unable to create a plug-in (e00002c7)
< waiting for device >
ERROR: Unable to create a plug-in (e00002c7)
Click to expand...
Click to collapse
hi,
plz try CWM, M8 got some issues with twrp.
philz_touch_6.26.6-m8.img is the stable version plz try that.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8
So I am starting to move forward :
I have followed the instructions to install philz_touch_6.25.5-m8.img by flashing it to my HTC where I get the setup screen for philz_touch_6.25.5-m8.img. I cleared the cache and I then installed the UPDATE-SuperSU-vx.xx.zip using the install zip from sdcard and then rebooted the HTC.
Unfortunately I have come back to the bootloader screen.
For what the instructions say it should be working now, but it does not seem to be?
Now it seems that whatever I try I cant seem to get past the bootloader....
And when I power down from the bootloader, It shuts down for a few minutes and then boots back into the bootloader.
Not sure what to do now?
millhhaus said:
So I am starting to move forward :
I have followed the instructions to install philz_touch_6.25.5-m8.img by flashing it to my HTC where I get the setup screen for philz_touch_6.25.5-m8.img. I cleared the cache and I then installed the UPDATE-SuperSU-vx.xx.zip using the install zip from sdcard and then rebooted the HTC.
Unfortunately I have come back to the bootloader screen.
For what the instructions say it should be working now, but it does not seem to be?
Now it seems that whatever I try I cant seem to get past the bootloader....
And when I power down from the bootloader, It shuts down for a few minutes and then boots back into the bootloader.
Not sure what to do now?
Click to expand...
Click to collapse
is your problem similar to this?
http://forum.xda-developers.com/showthread.php?t=2784232
May be you are using the wrong version.If you have international device you should try international version of philz/cwm recovery.I would suggest you to use TWRP since it is basically meant for htc devices.
Why am I getting this "FAILED (remote: image error! (BootMagic check fail))" error message all the time?
Davids-MacBook-Air:desktop millhhaus$ fastboot flash boot cm-10.2.1-m7ul.zip
target reported max download size of 1830711296 bytes
sending 'boot' (198067 KB)...
OKAY [ 6.904s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 6.905s
millhhaus said:
Why am I getting this "FAILED (remote: image error! (BootMagic check fail))" error message all the time?
Davids-MacBook-Air:desktop millhhaus$ fastboot flash boot cm-10.2.1-m7ul.zip
target reported max download size of 1830711296 bytes
sending 'boot' (198067 KB)...
OKAY [ 6.904s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 6.905s
Click to expand...
Click to collapse
because you are using M7 files mate. you need to use M8.
M7 - Htc one - 2013 model
M8 - Htc One - 2014 model
http://download.cyanogenmod.org/?device=m8
Posted in the general thread, but no replies.
I seem to have softbricked my phone by rooting then applying the OTA update. I've tried re-rooting, wiping cache, factory resetting, etc., and nothing seems to work. Following the steps in http://forum.xda-developers.com/zenf...d-zf2-t3127835 I can get to step 7, but when I submit any of the commands I get this:
Code:
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14822 KB)...
OKAY [ 0.666s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.839s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.545s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 0.716s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11868 KB)...
OKAY [ 0.522s]
writing 'boot'...
FAILED (remote: Permission denied
)
finished. total time: 0.694s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Permission denied)
finished. total time: 125.564s
It wasn't clear if it was a windows permission error or an android permission error, so I tried an admin command prompt but that didn't change anything.
Any suggestions? Thanks in advance
Bump in hopes of a solution
And another bump, any help would be greatly appreciated
I'm wondering if it has to do with having a bootloader installed being over a certain version. I had 2 Asus Zenfone 2s and I get the same error messages. I can't remember what my first ZF2 had for firmware to start, but I was a dummy and updated it all the way to 2.20.40.90 stock. Everytime I tried to write via fastboot, Permission Denied. My new ZF2 on 2.20.40.59 also has the same problem. I feel like Asus patched the ability to fastboot these files or something. Running CMD as Administrator doesn't help the situation.
bumping because I'm having the same issue, coming back to stock after having CM12.1
As easy as it sounds, the solution was just flashing the newest software from the ASUS website, using adb sideload UL-Z00A-WW-2.20.40.97-user.zip
I can't imagine why I wouldn't have done that sooner, but it fixed it. Whether that worked due to something else I did, i have no idea, but my phone is now working
I had that before but fortunately I was able to fix it.
Get a microsd, but a firmware from Asus website, make sure that it is the correct one if you have WW then download WW, download it from Asus website or it will not work.
Then put the micro sd on the phone., rename the file MOFD_UPDATE don't put zip cause it will be doubled.
Boot to bootloader then boot to recovery. Automatically the phone will restore itself.
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
I was also unable to mount the SD card, might have something to do with MOFD not being mapped.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
KylarBStern said:
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
ebanreb37 said:
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
I already tried it, I wrote in my post that I tried it. And it didn't work.
KylarBStern said:
I already tried it, I wrote in my post that I tried it. And it didn't work.
Click to expand...
Click to collapse
SD card MUST be FAT32 or 32gb or less. If you are using anything else it won't detect the sd card.
Cheers...
Ok it's been a while since I've tried anything with this phone and just now I did what you said, copied the firmware file which I downloaded from ASUS to a 2GB sd card formatted in fat32, rebooted to recovery phone applied the update sucessfully and restarted but I am still stuck in bootloop ? I tried every method so I asume the phone is ****ed and I should send it back for RMA ?
I flashed system.img and boot.img of Android 6 Factory Image manually and worked so far.After that i want a clean install,so i erased system,userdata and boot Partition and flashed the Factory Image with the included skript.But Android wasn't booting(i waited over 30-35 min.).So did the same again with no success.So i flashed TWRP and flashed CyanogenMod (that worked for me, but TRWP shows Mount Erros with data,cache etc.).But CyanogenMod also stucks in Bootanimation.
Have you tried re-downloading the files? It could be a bad download maybe.
theminikiller said:
Have you tried re-downloading the files? It could be a bad download maybe.
Click to expand...
Click to collapse
Yes.I also tried it with a Lollipop Factory Image.
david.mueller1013 said:
Yes.I also tried it with a Lollipop Factory Image.
Click to expand...
Click to collapse
+1
I have the same problem
Dirty flashed the android 6 flash-all.bat and now I am soft-bricked
Fastboot is activate but fails all actions
If you get an answer please let me know
david.mueller1013 said:
Yes.I also tried it with a Lollipop Factory Image.
Click to expand...
Click to collapse
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Nic2112 said:
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
Click to expand...
Click to collapse
Now short enough?
Nic2112 said:
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Click to expand...
Click to collapse
I tried it, but when i go into Stock Recovery, it shows the lying Android figure with exclamation mark.
Nic2112 said:
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Click to expand...
Click to collapse
Unfortunately the MultiROM version is not working,too.The normal version worked well for before(My device wasn't shipped with 5.0.1 or is from best buy or something like that).
david.mueller1013 said:
I tried it, but when i go into Stock Recovery, it shows the lying Android figure with exclamation mark.
Click to expand...
Click to collapse
That's normal, from there press power and Vol Up shortly after, you'll see a menu appear. Just wipe to factory default and reboot.
The first boot takes 3-5 minutes so let that go and you should be back in business.
Nic2112 said:
That's normal, from there press power and Vol Up shortly after, you'll see a menu appear. Just wipe to factory default and reboot.
The first boot takes 3-5 minutes so let that go and you should be back in business.
Click to expand...
Click to collapse
Thank you so much!It worked and booted succesfully , but i don't unterstand the error exacly.
But the main point is, it works again.I had some worse fears like corrupted memory.
How bout editing the thread title adding [solved]...
Nic2112 said:
Goodness your signature is long, who needs that level of detail on all the devices you own, really.
For your problem, boot in bootloader, run the flash-all batch file, when you seed the android boot animation hold power for 10 seconds, boot in recovery mode and do a factory reset to default.
Your recovery problem might be because you need the multi-ROM version of TWRP, I have to use that because if not, TWRP sees no partitions. For my nexus, every time I run the flash-all batch file, I have to do a factory reset to default.
Click to expand...
Click to collapse
Hi
I'm having a similar problem but the flash-all script cant write to my N7 it seems - as below
sending 'bootloader' (3911 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.602s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.024s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Power + Volume Up just bring me to looping Google screen and I only have access to fastboot screen
I hope you can help me too ?
Thanks
david.mueller1013 said:
Thank you so much!It worked and booted succesfully , but i don't unterstand the error exacly.
But the main point is, it works again.I had some worse fears like corrupted memory.
Click to expand...
Click to collapse
There is no error, some people can dirty flash the image and some can't. I know that when I flash the image, unless I do a factory reset the tablet never boots back. Maybe something that's left behind prevents the boot from completing.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
caolfin said:
Hi
I'm having a similar problem but the flash-all script cant write to my N7 it seems - as below
sending 'bootloader' (3911 KB)...
OKAY [ 0.156s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.602s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.024s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Power + Volume Up just bring me to looping Google screen and I only have access to fastboot screen
I hope you can help me too ?
Thanks
Click to expand...
Click to collapse
Is your tablet already in boot-loader mode when you start? If it is then maybe the bootloader has to be unlocked? I can't say for sure, I don't have a lot of experience messing with the tablet yet. I tried custom ROMS but I'm trying to stick to stock now.
Hi
Yes, the N7 is stuck in bootloader
I have tried many times to lock and unlock the bootloader and currently the last few lines of the bootloader screen are
SIGNING = yes
SECURE BOOT = enabled
LOCK STATE = unlocked
I am assuming that LOCK STATE means bootloader lock state and therefore this should be ok ?!
This is really stumping me now
Nic2112 said:
There is no error, some people can dirty flash the image and some can't. I know that when I flash the image, unless I do a factory reset the tablet never boots back. Maybe something that's left behind prevents the boot from completing.
---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------
Is your tablet already in boot-loader mode when you start? If it is then maybe the bootloader has to be unlocked? I can't say for sure, I don't have a lot of experience messing with the tablet yet. I tried custom ROMS but I'm trying to stick to stock now.
Click to expand...
Click to collapse
Hi, I tried to reset the bootloader and now I cant get it to unlock ggggrrrrr
Comes up with the questions Unlock Bootloader ? and I say yes
I get
C:\adb\razor-lmy47v>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 5.003s
I'm totally stumped now
can someone with LTE (razorg) please do the OTA using the bootloader method (wiping data and system first) and put TWRP back and then make a TWRP backup without booting into the fresh android install so that people who dont have working USB can possibly get the update. it would be much appreciated and theoretically should work.