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^^
Related
Hi all,
Im having a little trouble with my dhd. It won't boot up !
I can get into HBOOT, but thats it. (ie. no recovery CWM)
When trying to boot normally it hangs at spash screen.
so far i have tried:
- fastboot flashing (system.img dosn't flash (for known reasons))
- this thread (http://forum.xda-developers.com/showthread.php?t=841890) (tried with 2 different RUUs)
everything seemed to go according to plan, but still exactly the same problem.
- I've even tried flashing back the stock spash screen via fastboot in preperation to send it back to tmobile/htc to fix BUT, despite fastboot telling me flashing was succsessful, i still have my custom splash!
- pulling my hair out!
ive got eng hboot s-off radio s-off supercid and stuff??
my hboot info screen looks like this:
ACE PVT ENG S-OFF
HBOOT-0.85.2007 (PD9810000)
MICROP-0438
RADIO-26.04.02.17_M2
eMMC-boot
Oct 11 2010, 12:44:14
SYSTEM INFO
SN-HT0CPRX05836
LCD-SHARP
TOUCH PANEL-SYN3KT_0108
Commit-7eafc656
OS ver.-1.39.110.1
IMEI-
CID-11111111
RAM-768MB
eMMC-Sandisk 2223MB 4554751sectors
Thanks in advance to anyone with ideas
Which cw recovery is installed?
Sent from my Desire HD using XDA App
First question, what did you do immediately before you turned you DHD off, hence the reboot?
From the bootloader can you enter fastboot? You should be able to flash recovery from there. You mention "for known reasons" what are these?
Hi pwraggcan,
I'm not too sure? and I'm not sure how I can check either, as I can only enter hboot/fastboot.
AndyHarney,
As far as I can remember I was using my phone as normal. (no risky installs/flashes to speak of). Then overnight it ran out of battery, and now won't boot up .. ?
fastboot flash system system.img returns:
sending 'system' (410134 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
fastboot flash recovery recovery.img returns:
sending 'recovery' (8701 KB)... OKAY [ 1.494s]
writing 'recovery'... OKAY [ 0.837s]
finished. total time: 2.331s
but when I choose 'RECOVERY' form hboot menu it still hangs on splash.
jason9 said:
Hi pwraggcan,
I'm not too sure? and I'm not sure how I can check either, as I can only enter hboot/fastboot.
AndyHarney,
As far as I can remember I was using my phone as normal. (no risky installs/flashes to speak of). Then overnight it ran out of battery, and now won't boot up .. ?
fastboot flash system system.img returns:
sending 'system' (410134 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
fastboot flash recovery recovery.img returns:
sending 'recovery' (8701 KB)... OKAY [ 1.494s]
writing 'recovery'... OKAY [ 0.837s]
finished. total time: 2.331s
Click to expand...
Click to collapse
So you have recovery, and you're rooted, well I'd say install a ROM as ROMS flash system, boot and cache img files. Sending a 410mb file ofver adb seems a bit risky. Also, if you have no ROMs on the SD Card go into recovery, mounts and storage and at the bottom is usb or something.
MrYuiM,
I don't mean to act the fool, but I don't fully understand you're post.
"well I'd say install a ROM as ROMS flash system, boot and cache img files"
not sure how I can go about doing this? using fastboot?
"Also, if you have no ROMs on the SD Card go into recovery"
which ROMs do you mean? I have on my sdcard "LeeDrOiD_HD_V1.5.1.zip" and others. I also have some nandroid backups.
Currently, I have not found a way to enter recovery..
P.S I apologize for spewing my ignorance all over this thread.
Get PD98IMG.zip from my downgrade guide, put it into your SD card and go to the bootloader. Then tell us what what happens.
By the way, you still have fully warranty despite the fact that your device has S-OFF. There is nothing about software mods in warranty terms. For example mike1986 sent his phone to HTC's service center, it was S-OFF and it even had a custom ROM in it, and they did not complain.
jkoljo said:
Get PD98IMG.zip from my downgrade guide, put it into your SD card and go to the bootloader. Then tell us what what happens.
By the way, you still have fully warranty despite the fact that your device has S-OFF. There is nothing about software mods in warranty terms. For example mike1986 sent his phone to HTC's service center, it was S-OFF and it even had a custom ROM in it, and they did not complain.
Click to expand...
Click to collapse
When I asked HTC they were pretty stern on the fact that rooting voids their warranty despite it not being in the guidelines :/
jason9 said:
MrYuiM,
I don't mean to act the fool, but I don't fully understand you're post.
"well I'd say install a ROM as ROMS flash system, boot and cache img files"
not sure how I can go about doing this? using fastboot?
"Also, if you have no ROMs on the SD Card go into recovery"
which ROMs do you mean? I have on my sdcard "LeeDrOiD_HD_V1.5.1.zip" and others. I also have some nandroid backups.
Currently, I have not found a way to enter recovery..
P.S I apologize for spewing my ignorance all over this thread.
Click to expand...
Click to collapse
To enter recovery turn your phone off completely and plug it into the charger, recovery will auto open. Also, everyone starts off somewhere.
But go with jkoljo first as he is more experienced
Hi jkoljo,
Downloading now,
It's also a big relief to hear that software modding dosn't effect warrenty *phew*
jason9 said:
Hi jkoljo,
Downloading now,
It's also a big relief to hear that software modding dosn't effect warrenty *phew*
Click to expand...
Click to collapse
Good luck mate, report back on how it goes
Might be futile but you could try a different recovery. If you're s off it should work. Try a 2.x.x.x then a 3.x.x.x. flashing from fastboot, it could be that. If the pd98img doesn't work then it might be a faulty motherboard and htc will have to fix it.
Sent from my Desire HD using XDA App
I tried jkoljo advice, but still no dice! ... (hey that rhymes!)
One thing I noticed as it was checking SD card: -
SD Checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nbh]
No image or wrong image!
Loading...[PD98IMG.zip]
are those errors normal?!
just to clarify, after jkoljo's PD98IMG.zip update, I reboot and it hangs at my custom spash screen, just as before.
It's as if I hadn't tried to update/recover at all!
Anyways, Thankyou all for your help, assistance and advice.
I have to go out now, but ill be back tomorrow to try again.
It seems that you have to format your SD card. Do a full format to FAT32 (no quick format), and try it again.
Ok, formatted and tried again.
But same results as my last post.
I even tried with 2 SD's (4gb + 8gb).
Does this mean my phone is not recoverable..?
....I hope not..
oopes, delete this post please
pwraggcan said:
Try flashing a different recovery while in fastboot.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Could you recommend one?
The only one I've ever known is CWM.
Also I don't have much faith in fastboot right now.
When I flashed my stock splash, it said 'OK' but never changed!
Thanks pwraggcan
Try flashing a different recovery while in fastboot.. Try the stock one first and if you can boot into recovery wipe data/factory reset.
fastboot flash recovery nameofrecovery.img
recovery zip attached. good luck.
Thanks for the suggestion pwraggcan,
I tried that recovery.. and it flashed 'OK' but still no change from my previous attempts.
Soo... Shall I call this a write-off and let HTC deal with it..
Or are there any last ditch solutions I could be trying.
Jason9
As a last resort try the attached recovery. If this recovery doesn't work it's gotta be a hardware issue. I'm thinking if you backed up with a 2 series cw recovery then updated the recovery with rom manager to a 3 series cw recovery it won't let restore the backup. So, try the attached and fingers crossed, you're up and running. Probably won't sort it but definitely worth a try.
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:
Hello
i have some problems with my HTC One X. Until 2 hours ago it worked perfectly and without problems. i didn't flash anything in the last few weeks, but theres ARHD (ICS) installed. But then suddenly it had a freeze, so i had to restart it with pressing the powerbutton for 10 seconds. Since then, it doesn't boot anymore and also i can't access the Recovery, i get a blackscreen if i try, But i come into the Bootloader, Fastboot is possible but doesn't work...
I tried to reflash the Boot.img, but there was an error: erasing cache FAILED (remote: 19000008)
I also tried to reflash the CWM Recovery but there was another error:
5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.904s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: (00030000))
finished. total time: 1.150s
So can anybody help me? All that I want is access to my virtual SD Card for saving my data, and can anybody tell me how and if I can "repair" my One X? And sorry for the bad english, i'm no native speaker...
you can try this, http://forum.xda-developers.com/showthread.php?t=1609190
Thanks, but it didn't help. When i tried to flash the images in fastboot almost the same errors as before occured...i absolutely dont know what to to now, i think i even can't relock the bootloader, flash the stock recovery and a RUU
Achsoistdas19 said:
Thanks, but it didn't help. When i tried to flash the images in fastboot almost the same errors as before occured...i absolutely dont know what to to now, i think i even can't relock the bootloader, flash the stock recovery and a RUU
Click to expand...
Click to collapse
what the error mate?
Hm, i don't really know. There are these Error-Codes, mostly "remote: 19000008" or "remote: 00000004" also with a 5 at the end, and it says "remote: not allowed" sometimes.
Hi guys, posted this under the TWRP thread but realised it might be a more general problem
ISSUE: I believe I bricked the phone or bootloop (sorry not familiar with terminology). After the splash screen the word ASUS shows with a never ending circle loading sign under it. I can't enter recovery using Power + Vol down
BACKGROUND: I am having some issues after doing the Tethered Recovery. I am rooted and have bootloader unlocked. Once I used cai_dat_CWM.bat and was in recovery, I tried to flash the clean rom HarfainX, but before I did, I did a wipe of Cache and it said formatting cache but after 10 minutes didnt load. So I turned off the phone, now it hangs on the ASUS screen. I can enter fast boot, but I cant enter recovery mode.
Can anyone help me in getting it back running again?
Update:
Tried doing a wipe through fastboot -w
and got the following results:
Erasing 'userdata' OKAY
Sending 'userdata' OKAY
Writing 'userdata' FAILED (remote: flash_cmds error!)
Thanks
You should've waited.
Posted using my phone.
jose makalolot said:
You should've waited.
Posted using my phone.
Click to expand...
Click to collapse
I did wait it just didn't do anything for about 10 minutes.
I'm trying to sideload using ADB the stock rom from ASUS / Garbage free ROM by Harfain X and I am getting:
adb.exe sideload update.zip
loading: update.zip
error: device not found
fastboot update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
Anyone can offer suggestions?
...Flashed untethered TWRP... fixed the problem .. thanks TheSSJ for creating it
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.