Hello,
Sorry but I have ran into a pretty big problem and I was an idiot and did not make a NAN backup.
I am capable of going to the bootloader and I can flash recovery but I can't do much else as far as updating the bootloader from 4.18 to 4.23 (not a huge issue at least right now) but the bigger issue is that I cannot flash system.img as it will just timeout on "sending system" through fastboot. Sending myself a custom rom through ADB and attempting to flash recovery does not work either due to system partition errors. erased and retried to send system and no luck, continues to time out. I believe this might be due to my previous custom rom perhaps resizing the system partition too small? But shouldn't this be solved when erasing/using flash-all.bat??
Please not sure what to do at this point. I've been using the Nexus Root Toolkit trying to flash 4.2.2, as I don't have the bootloader for 4.3 on my device (can't update it anyhow.. again that's a problem but I should be able to at least flash 4.2.2 for right now?) and doing it manually with fastboot and ADB but I am have no luck getting system to write/finish sending.
Any recommendations would be greatly appreciated!!
You can boot into recovery (boot/stock ) directly from botloader via fastboot. Hard to say if it is usefull to you.
Unfortunately not. I can get to recovery and flash custom recoveries with no problem, it is sending the system.img and getting it to write the problem.
Is a picture of the problem, just times out when sending the system.img even if I leave it on for 1 hr.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The same happens at sending the bootloader you see but I disconnect and reconnect quick to make sure it gets past this (I have the 4.18 bootloader already loaded, and I cannot update this but this seems like a second issue compared to sending the system.img). Doing it manually through fastboot and flash-all.bat doesn't help, still times out. Sending myself a rom to flash through recovery doesn't work as I have system and cache partition issues that won't let it install.
Not sure what to do at this point other than keep trying and maybe I'll get luck?
xdaNoobTutorial said:
Unfortunately not. I can get to recovery and flash custom recoveries with no problem, it is sending the system.img and getting it to write the problem.
Is a picture of the problem, just times out when sending the system.img even if I leave it on for 1 hr.
The same happens at sending the bootloader you see but I disconnect and reconnect quick to make sure it gets past this (I have the 4.18 bootloader already loaded, and I cannot update this but this seems like a second issue compared to sending the system.img). Doing it manually through fastboot and flash-all.bat doesn't help, still times out. Sending myself a rom to flash through recovery doesn't work as I have system and cache partition issues that won't let it install.
Not sure what to do at this point other than keep trying and maybe I'll get luck?
Click to expand...
Click to collapse
Just to update ** I am using Windows 8 and think this might potentially be just a driver problem. Not sure exactly why, since I can easily write recovery and boot images... but this is the only thing I can think of preventing the bootloader and system to write/send?
*** UUPDATE********
Soooo Sucesss!
Was the mother front-dooring USB port the entire time. Tried it on another laptop /w Windows 7 and had issues, went back to my Winodws 8 and plugged it into my OTHER usb port (oddly enough, the USB 3.0 port) and SUCESS!!! Flashed the bootloader again (probably didn't need to but I wanted to for spite), flash recovery, flashed boot.img, flashed system.img, and started and now I am back at stock firmware ready to go play the dangerious game of custom roms again, since I never learn from my misfortunes.
Also oddly enough my data partition was taking up EVERYTHING too, so this might have added to the issues. Why it took up the entire free space on the internal sd I do not know, likely just a bunch of 0's for some reason or another. So formatting that through TWRP might have also helped.
For others who might run into this problem:
First of all wipe everything via fastboot or TWRP (i prefer fastboot in case)
fastboot erase system
fastboot erase data
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
then re-flash from the stock firmware from google (extract the .img files from the .zip on the tarball) and flash through flashboot
fastboot flash system system.img (or a custom ROM img if you'd like)
fastboot flash recovery recovery.img (or a custom recovery img if you'd like)
fastboot flash boot boot.img (or a custom boot img if you like)
MOST IMPORTANTLY IF YOU'RE NOT ABLE TO FLASH MAKE SURE YOU TRY OTHER USB PORTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
HTH to anyone in the future
xdaNoobTutorial said:
*** UUPDATE********
Soooo Sucesss!
Was the mother front-dooring USB port the entire time. Tried it on another laptop /w Windows 7 and had issues, went back to my Winodws 8 and plugged it into my OTHER usb port (oddly enough, the USB 3.0 port) and SUCESS!!! Flashed the bootloader again (probably didn't need to but I wanted to for spite), flash recovery, flashed boot.img, flashed system.img, and started and now I am back at stock firmware ready to go play the dangerious game of custom roms again, since I never learn from my misfortunes.
Also oddly enough my data partition was taking up EVERYTHING too, so this might have added to the issues. Why it took up the entire free space on the internal sd I do not know, likely just a bunch of 0's for some reason or another. So formatting that through TWRP might have also helped.
For others who might run into this problem:
First of all wipe everything via fastboot or TWRP (i prefer fastboot in case)
fastboot erase system
fastboot erase data
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
then re-flash from the stock firmware from google (extract the .img files from the .zip on the tarball) and flash through flashboot
fastboot flash system system.img (or a custom ROM img if you'd like)
fastboot flash recovery recovery.img (or a custom recovery img if you'd like)
fastboot flash boot boot.img (or a custom boot img if you like)
MOST IMPORTANTLY IF YOU'RE NOT ABLE TO FLASH MAKE SURE YOU TRY OTHER USB PORTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
HTH to anyone in the future
Click to expand...
Click to collapse
You just saved my ass! i was experiencing this exact problem! i could not for the life of me figure out why my shield tablet was flipping out when i tried to flash the system image! read this post, switched USB ports, and BOOM!
thanks dude!
Related
As it says above THIS is why i cant boot up hero roms or any other that doesnt use cupcake/donut boot does ANYBODY have ANY IDEAS!!??!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also tried using adb shell to flash the boot but get error writing on block xxxxxxxxxx
I used RA_dream-v1.2.2 today threw ADB. Placed .img on root of sd,
Dont use mount -a, mount /system, or mount /sdcard
Just use
# mount
# flash_image recovery /sdcard/recovery-RA-dream-v1.2.2.img
http://forum.xda-developers.com/showthread.php?t=566669
Its the boot img that wpnt flash not the recovery but thanks anyhow
bumping this thread as i am pretty stuck.Not being able to write the boot.img means even my nandroid wont work
can you get a different boot.img to try it might be curupt
found this
http://forum.xda-developers.com/showthread.php?t=509248
use adb shell
also i see you deleted recovery installed new recovery removed system then you tried to install boot
did you try to install system first before both recovery and boot
i'm no expert lol
found some other stuff
How to restore from your backup file
1. Download one of the above signed SPL updates and rename it to update.zip
2. Copy update.zip to the root of your SD-card
3. Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder C:\Android.
4. booting your Magic into recovery model
5. select [Alt + S] – Apply sdcard:update.zip
6. select [Home + Back] – reboot system now
7. After reboot it will update upgrade/downgrade your SPL version, then power off your Magic again
8. Push “Back” + “Power” to HBOOT model
9. double check your SPL version is upgrate/downgrate
10. Plug the USB cord back into your phone. The screen on your phone should say fastboot.
12. Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
13. Type cd C:\android
11. then enter the following commands C:\android >
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
12. After reboot your Magic, it need about 2-5 min to restore
13. then a band new original Android 1.5 is restored
Yes i have tried that, The problem is the boot.img. I cant flash it! Nandroid restore fails due to boot.img (cannot be flushed!) Thanks for the speed yresponse but still no joy
bonesy said:
Yes i have tried that, The problem is the boot.img. I cant flash it! Nandroid restore fails due to boot.img (cannot be flushed!) Thanks for the speed yresponse but still no joy
Click to expand...
Click to collapse
Did you follow ALL steps while rooting your 32B?
I'm almost 100% sure that you are using your 32B with a 32A radio and rom, right? Complete the rooting by following the "Revert to 32B Radio and ROM" exactly to the letter in this thread. Do not try to do something else or you'll brick it.
i followed all steps apart from using the gold card as i couldnt make one and reverted back to 32B using your steps. I also did it all again but using flashrec.apk?
try this flashrec.
worked for my 32A
http://zenthought.org/content/project/flashrec
Done the flashrec thing, Quite a few times now i have a feeling as it was repaired by htc and sent back they have made it so the boot.img cannot be written in any way, If i use a friends nandbackup of hero it fails (not that it says so) and just keeps on the splash screen untill the phone becomes so hot it switches off! Giving up on this, Gone back to standard (rooted) rom and will await the sense update (fingers crossed)
Stil lthe same problem...although it WILL let me flash sapphire boot just not a modified boot see here....
First flashed boot.img is the google ion boot off of the htc site
Second is the tattoo boot.img modified for the sapphire. Any ideas?
Anyone know where i can get the Google Ion hboot from? just wanna try one more thing before i give up!
Have you posted this in Dream Q&A? That forum is way more active and there is alot more knowlege on things like this. Maybe send David1077 a PM. I feel bad because I have looked at your post for quite a few weeks now with little help. Good luck
i would but am afraid of a ban for posting in wrong forums,ive already done that lots!
somprogress
seems lile i can fastboot boot the img but it just loops at the boot screen?as i say donut roms work fine but ANY sense ui fail at line 92
Right im now offering £25 if anyone can get sense ui working on my phone.any info they need i will give!
bonesy said:
Stil lthe same problem...although it WILL let me flash sapphire boot just not a modified boot see here....
First flashed boot.img is the google ion boot off of the htc site
Second is the tattoo boot.img modified for the sapphire. Any ideas?
Anyone know where i can get the Google Ion hboot from? just wanna try one more thing before i give up!
Click to expand...
Click to collapse
http://www.4shared.com/file/143324302/e942c9d8/boot.html
not to sure what your asking for but this is a boot.img from my signed-google_ion-img-14721
have you looked here iknow you would of but just in-case
http://developer.htc.com/google-io-device.html
my original boot.img
http://www.4shared.com/file/143325952/211edf2e/_2__boot.html
this one is from inside the MLIGN-MagicV1.0-FINAL rom
http://www.4shared.com/file/143326459/aca13a1b/_3__boot.html
the problem is i cant write the boot img in any way.Only original boot.img files not any that are modified.
Its the HBOOT i need to try, But thanks
bonesy said:
the problem is i cant write the boot img in any way.Only original boot.img files not any that are modified.
Its the HBOOT i need to try, But thanks
Click to expand...
Click to collapse
so what is the hboot?
what are you excactly asking for
The hboot is the spl, im asking for the dev one as its naturally enabled for fastboot therefore im trying to trick my phone to make it think its the dev phone (Google ion) hopefully bypassing the "REMOTE: image update error'' when writing boot.img
have you tried the one i'm on Engineering SPL 1.33.2004 by Crios
Engineering SPL 1.33.2004 by Crios is actually a hex-edit of SPL 1.33.2005 to fool updates.
Hello there!
I have a Nexus 7 Device, I rooted it using a toolkit, everything was working great, then I messed up a little and I need to restore it using a Factory Image (a.k.a Stock ROM)...
The problem is, when I try to flash the .zip, it gives me the following error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to some tutorials, you type the following commands to flash a ROM:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update ROM.zip
Click to expand...
Click to collapse
Because I'm afraid of something going wrong, I didn't erased any partition, so if for some reason the flashing procedure stops, I have the old data/partitions working because I didn't erased any, I just used the following command:
fastboot -w update ROM.zip
Click to expand...
Click to collapse
So, the questions are:
Do I need to erase the partitions first before trying to flash the Stock ROM?
Should I try flash each .img separately?
Additional Information:
Android is working, I'm able to boot with success.
Bootloader unlocked.
I didn't flashed any custom Bootloader/Recovery/ROM, everything is from Factory/Stock.
I have tested flashing the ROM under Windows and Linux (Ubuntu), it gives me the exact error.
The .zip I'm using isn't corrupted. (And it's directly from developers.google.com)
If flashing without erasing the partitions worked, I would erase them (To delete ALL data/trash) and flash it again...
P.S: First post!
I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Hello!
Thanks for the answer, I tried to flash system.img and it worked, fastboot automatically erases the system partition.
I have now a clean system, thanks!
For other people with the same problem as me:
1 - Enter Fastboot Mode
2 - Extract system.img
3 - Run "fastboot flash system system.img"
4 - Enter Recovery Mode and do a "Factory Reset" (Optional, I guess)
5 - Enjoy!
Spenzert said:
fastboot automatically erases the system partition.
Click to expand...
Click to collapse
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers
bftb0 said:
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers
Click to expand...
Click to collapse
I believe fastboot really erased the partition, there's no "SuperSU" anymore and I have attached a screenshot of fastboot erasing the partition.
Cheers!
I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?
bftb0 said:
I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?
Click to expand...
Click to collapse
Android SDK Manager says "Rev. 16.0.1" (Platform-tools), maybe fastboot erased the partition first because I used "fastboot flash" instead of "fastboot update"...
A little off-topic:
I tried to root manually my Nexus and it's really easy, I might make an updated tutorial soon on how to root it manually
Have a good day!
Edit: I tried to flash TWRP (Recovery) and it didn't erased the partition first.
Hello together,
these were the steps to update to 5.1.1 (LMY47X) from 5.0.1 (LRX22C).
It was working for me - without loosing data.
Notes:
OTA didn't work cause of having custom recovery / root.
Maybe it was also in another thread here - but I didn't saw it
It work for me (WIFI-Version) - but might kill your device :crying:
from post #4: In case you using fastboot no very often - look here for more details: http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26 - Thanks the.teejster
Steps
Make sure you have working fastboot on your PC
Download Factory Image and unzip it
Also unzip the included image-volantis-lmy47x.zip
Boot your Nexus 9 into fastboot (Shutdown device; Hold Vol-UP + Power on)
Flash bootloader & reboot
Code:
fastboot flash bootloader bootloader-flounder-3.44.1.0123.img
fastboot reboot-bootloader
Erase everthing but data partition
Code:
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase vendor
Flash the file (found in the unpacked image-volantis*zip)
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Reboot device
Optional: Root it again.
Download CF-Autoroot
Use the root-Scripts
Hope it helps and works for you.
One question. I am rooted and have twrp recovery. I this case : Why should we update recovery?
Alternatively, you could remove the "-w" flag from the flash-all.sh script and run it without losing data
A few key prerequisite items are missing in the OP..
I wrote up a similar "how to" over here :
http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26
Hello,
I always upgraded android manually flashing while in fastboot.
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And lot of apps force close (gmail opens, but when i try to open a mail fc, eurosport same, opens but when i reada news fc, and many other)while others works flawless.
I tried wiping everything, also userdata, but problem not solved.
What can i do?
I read here that someone when upgrade android also erase "vendor", it's the only thing i didnt do, but i never did it.
Please help, finally with 5.1.1 this device flies but now i can't use it!
Thanks.
What about Vendor and recovery ?
Please see my instructions linked about 2 posts up. Follow those exactly and you shouldn't lose any data and the upgrade should be fine.
Sayan1987 said:
Hello,
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
Click to expand...
Click to collapse
Sayan1987 said:
Hello,
I always upgraded android manually flashing while in fastboot.
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
And lot of apps force close (gmail opens, but when i try to open a mail fc, eurosport same, opens but when i reada news fc, and many other)while others works flawless.
I tried wiping everything, also userdata, but problem not solved.
What can i do?
I read here that someone when upgrade android also erase "vendor", it's the only thing i didnt do, but i never did it.
Please help, finally with 5.1.1 this device flies but now i can't use it!
Thanks.
Click to expand...
Click to collapse
try fastboot flash vendor vendor.img
For the fc you are experiencing, it is possibly due to the modified ART in 5.1.1 or you check if you have the latest Android Webview
I just thought I would throw this out here in case anyone needs or wants to know...
You do not need to flash the bootloader to upgrade from 5.0.2 to 5.1.1, I can not tell you if this will work coming from 5.0.1
Also after first boot and you flash twrp, you can boot to recovery then immediately reboot back to system. Twrp will install su for you. You'll just need to update the su apk in the market. No need to mess with any kind of su zip anymore.
That's all I have to add to an already great guide.
the.teejster said:
What about Vendor and recovery ?
Please see my instructions linked about 2 posts up. Follow those exactly and you shouldn't lose any data and the upgrade should be fine.
Click to expand...
Click to collapse
laill said:
try fastboot flash vendor vendor.img
For the fc you are experiencing, it is possibly due to the modified ART in 5.1.1 or you check if you have the latest Android Webview
Click to expand...
Click to collapse
Thanks guys flashing vendor fixed everything!!
All the forced closes, heat problems, May I ask are you really stock? No such problems here
Verstuurd vanaf mijn HIGHWAY SIGNS met Tapatalk
i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
stargirl29 said:
i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
Click to expand...
Click to collapse
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.
fastboot
Evolution_Tech said:
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.
Click to expand...
Click to collapse
i'm not really sure how to do that.
stargirl29 said:
i'm not really sure how to do that.
Click to expand...
Click to collapse
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot
fastboot
Evolution_Tech said:
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.
stargirl29 said:
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.
Click to expand...
Click to collapse
Factory reset from recovery.
Evolution_Tech said:
Factory reset from recovery.
Click to expand...
Click to collapse
if you mean this, https://support.google.com/nexus/answer/4596836?hl=en
yes. that was the first thing i did. and always the first thing i try before using any toolkits or manual repairs.
i ran Wugs again today and FINALLY got it back to the sign in screen to setup the tablet. everything was going great. then i got back into the bootloader to lock the oem. and when it restarted i'm still getting the "optimizing apps x of 99" which is annoying but it seems my tablet is at least usable for now.
Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.
fixed it!
vipthomps said:
Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.
Click to expand...
Click to collapse
i fixed it with Wugs yesterday, finally! after 5 days of trying.
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP
is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?