My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Things to try
acesofbelkan said:
My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Click to expand...
Click to collapse
It looks like you've tried just about everything and you are very capable of getting it done. My only suggestion is that when I thought I was bricked, I kept wiping all the data I could find. From CWM I started with a wipe data/factory reset and that had the best results for me. After that, wipe dalvik, wipe battery stats, and I tried loading a new ROM from sdcard. I wouldn't try to install a new kernel or any other mod until you successfully boot into your new(or old) ROM.
Like I said, you probably already knew all of this but I wanted to make sure all the bases were covered. If it doesn't help you, I hope it at least helps someone else. Good luck, and please post your progress!
try using fastboot to erase the system and other partition.
fastboot erase system
fastboot erase userdata
faseboot erase boot
fastboot erase recovery
Then flash stock from fastboot
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
acesofbelkan said:
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
Click to expand...
Click to collapse
Fastboot does not require mounting of anything -- it writes to the entire partition.
efrant said:
Fastboot does not require mounting of anything -- it writes to the entire partition.
Click to expand...
Click to collapse
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
acesofbelkan said:
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
Click to expand...
Click to collapse
No. Root has nothing to do with fastboot. Root has nothing to do with your device. Root has to do with the Android build that you are running.
When you are booted into the bootloader (i.e., fastboot mode), there is no Android OS running, so how can there be root?
The fastboot executable on your PC interacts directly with the bootloader, and it will wipe an entire partition, or write an image to a partition.
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
NoorGnex said:
[snip]
first off you need to download wugfresh's Gnex toolkit
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1469909
efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
I've personally never had problems with tool kits and have found them very helpful, because of my busy schedule I don't have the time to do it myself even with my amateur coding skills, and have found only people who dont understand what there getting themselves into get bricked, thats not to say you cant brick your phone if your smart but if your smart you would have done a nandroid before flashing anything.
thanks again for that enlightening post
NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
Click to expand...
Click to collapse
Link is bringing up a 404 error. Did the toolkit move locations?
JackG058 said:
Link is bringing up a 404 error. Did the toolkit move locations?
Click to expand...
Click to collapse
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
NoorGnex said:
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
JackG058 said:
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
Click to expand...
Click to collapse
This is what you should be reading for due diligence...
efrant said:
This is what you should be reading for due diligence...
Click to expand...
Click to collapse
I will add this to my reading list, and send you my kind thanks.
edit: And bookmarking, of course.
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
That's what I was trying to get across earlier...
Use this: http://forum.xda-developers.com/showthread.php?t=1626895 That way, you can see where you are having issues.
And in case you missed it earlier: http://forum.xda-developers.com/showpost.php?p=30015315&postcount=9
NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
Click to expand...
Click to collapse
Only after you learn what is going on in the background.
I think i'm going to stop trying to help people using toolkits if it seem that they did not even bordered to read up on fastboot and adb..
efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
+1
acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
This quote pretty much defines why people hate toolkits.
Related
i rooted my galaxy nexus last night, and today i was trying to put a rom on it, i went to wipe the cache, and now it wont boot past the google screen and im freaking out!
Before you flashed did you wipe system? Huh I bet not even so you only mention wipe cache....what about data , dalvik ?
Did you read directions in the op for the ROM?
Sent from my SPH-D710 using Tapatalk 2
it told me to wipe to factory, i tried doing that and it just froze, and now it wont boot. im trying to figure all this out but im a little over my head unfortunately.
Try booting into recovery and then wiping and flashing your ROM
i was trying to flash the codename android 1.6 rom, i cant post the link it wont let me
when i boot into recovery mode, it shows a droid with its chest open and a red exclamation point
I've never heard of that ROM but in fastboot will it let you use your volume and power keys to navigate to recovery? If not, try using fastboot commands on the computer to get into recovery (if you can? I'm not too acquainted with fastboot commands)
i can get into recovery but then it shows the droid with the red alert
m4gkman said:
i can get into recovery but then it shows the droid with the red alert
Click to expand...
Click to collapse
That's fastboot. Try looking into fastboot commands and see if any command will let you boot into recovery from there.
You buggered the boot image... Just flash it again, via fastboot...
They are normally in .Franco kernels...
you mean through terminal and stuff? my knowledge to this stuff is still pretty basic so im trying to grasp all of this
familyguy59 said:
You buggered the boot image... Just flash it again, via fastboot...
They are normally in .Franco kernels...
Click to expand...
Click to collapse
so fastboot is throught he computer?
m4gkman said:
so fastboot is throught he computer?
Click to expand...
Click to collapse
Yes. Fastboot is used, in CMD (Windows) Gnome terminal (Ubuntu/Linux distributions) and the Mac OS terminal...
You need to install the ADB drivers and download the fastboot/adb files first, though (Check the Windows 8 thread (In my signature), all you need is in there...
Or, download a .Franco kernel (Check the developement section, for your device (GSM/verizon/Sprint) and search the forum...
i did fastboot and all that stuff on my laptop at home(the one i rooted it with), do i basically need to redo all of that?
m4gkman said:
i did fastboot and all that stuff on my laptop at home(the one i rooted it with), do i basically need to redo all of that?
Click to expand...
Click to collapse
Yes, but just flash the boot.img
Code:
fastboot flash boot %Userprofile%\Downloads\<Whatever the file is named>.img
Ngo93 said:
That's fastboot. Try looking into fastboot commands and see if any command will let you boot into recovery from there.
Click to expand...
Click to collapse
No, that is not fastboot. That is recovery. He has the stock recovery flashed, which is the Android lying on its back with a red exclamation point.
m4gkman said:
i can get into recovery but then it shows the droid with the red alert
Click to expand...
Click to collapse
You need to flash CWM before you do anything else. Get it from the link in my signature and flash it in fastboot. Then boot into CWM, do a wipe, and re-flash the ROM you want.
efrant said:
No, that is not fastboot. That is recovery. He has the stock recovery flashed, which is the Android lying on its back with a red exclamation point.
You need to flash CWM before you do anything else. Get it from the link in my signature and flash it in fastboot. Then boot into CWM, do a wipe, and re-flash the ROM you want.
Click to expand...
Click to collapse
We've been there. Done that and got the T-shirt. The phone is working fine. Just installing CND 1.6
familyguy59 said:
We've been there. Done that and got the T-shirt. The phone is working fine. Just installing CND 1.6
Click to expand...
Click to collapse
No, he hasn't been there, and obviously you didn't understand that.
If he sees the Android lying on his back with the red ! then he has the STOCK recovery flashed, not CWM.
efrant said:
No, he hasn't been there, and obviously you didn't understand that.
If he sees the Android lying on his back with the red ! then he has the STOCK recovery flashed, not CWM.
Click to expand...
Click to collapse
CWM is flashed, it's installing CND (Or has installed) but whatever we do, it's a bootloop. lol) I'm doing everything, with him, whilst he's at work, via TV ^^
I'm seing exactly everything, what is happening, on the computer. I flashed everything myself...
familyguy59 said:
CWM is flashed, it's installing CND (Or has installed) but whatever we do, it's a bootloop. lol) I'm doing everything, with him, whilst he's at work, via TV ^^
I'm seing exactly everything, what is happening, on the computer. I flashed everything myself...
Click to expand...
Click to collapse
Ah, ok! None of that was mentioned in the thread. Had no idea that you were helping him -- I thought you were helping him in this thread.
Dear All
yes, I am new and I feel exactly as the intro-video when registering was referring to ("noob", "loser",...)
After half a year, thought it was time to root my galaxy nexus. Used the Gnexus Toolkit. Everything worked fine.
So, I wanted to take things a bit further and as I've read interesting things on the franco.kernel, I tried to flash a new kernel using the app's automatic flash tool.
Device restarted, stuck at the Google logo.
I went inro recovery mode and followed some guidelines I found here and on other fora telling me to wipe data, wipe cache, wipe dalvik cache, format data,....
First tried to restore the "recovery"-thing clockworkmod creates for you when first using it. Didn't work.
Tried to wipe/format once again... Nothing helps and now I've even lost the "recovery"-thing.
only option seems to adb sideload... but I do not seem to get that working.
Well... hm. Here I am then. Having no idea to continue...
And, yes,... I have to repeat... I feel exactly as the intro-video of xda is suggesting I should feel
Install GNex TOOLKIT in the PC, download a custom rom and push the file to the phone with adb in fastmode. With this toolkit you can also flash recovery (CWM for example) again.
http://forum.xda-developers.com/showthread.php?t=1392310
joooe said:
Install GNex TOOLKIT in the PC, download a custom rom and push the file to the phone with adb in fastmode. With this toolkit you can also flash recovery (CWM for example) again.
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
Thanks: I was indeed able to start in fastboot and used the Gnex Toolkit. I installed the stock image (4.0, then it updated to 4.2.1 later).
Pfffew, everything now works. hehe.
Thanks.
:good: Good result then.
joooe said:
I would probably start all over again.
Download latest version of ClockworkMod Recovery, go to fastboot mode, flash it.
Download rom, push it to the "sdcard" with adb, then go to CWM recovery and flash the rom.
Click to expand...
Click to collapse
That's indeed what I wanted to do.
Need to get some work done now. Will try it in the weekend. Thanks for the help.
I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs
Hey guys, I'm new to the HTC one, and I made a mistake. I accidentally formatted my device, the sdcard, firmware, and data, and I'm unable to mount the sdcard and data. I have clockworkmod recovery installed, and the bootloader unlocked, but I'm unable to do much else. When I attempt to flash a rom using sideloader, the screen will just reboot several times. I tried two different roms, CyanogenMod and Stock Rom, by either installing through sideloader or adb, but again, I can't see my SD card. I need help.
How can I fix my phone at this point? I'd be okay with either Stock Rom or CyanogenMod, I just need my phone working.
Please give a newbie a hand guys.
Thanks in advance.
dddmcd77 said:
Hey guys, I'm new to the HTC one, and I made a mistake. I accidentally formatted my device, the sd and data, and I'm unable to mount the two. I have clockworkmod recovery installed, and the bootloader unlocked, but I'm unable to do much else. When I attempt to flash a rom, the screen will just reboot several times. I tried two different roms, CyanogenMod and Stock Rom, by either installing through sideloader or adb, but again, I can't see my SD card. I need help.
How can I fix my phone at this point? I'd be okay with either Stock Rom or CyanogenMod, I just need my phone working.
Please give a newbie a hand guys.
Thanks in advance.
Click to expand...
Click to collapse
I don't know, but maybe try loading this by following the directions. Maybe you formatted the actual OS completely? This will get you to CM and then from there hopefully flash again
http://wiki.cyanogenmod.org/w/Install_CM_for_m7vzw
Also, try rebooting JUST the recovery, because then your SD shows up again.
Sent from my HTC6500LVW using Tapatalk
thanks for the reply
justinisloco said:
I don't know, but maybe try loading this by following the directions. Maybe you formatted the actual OS completely? This will get you to CM and then from there hopefully flash again
Also, try rebooting JUST the recovery, because then your SD shows up again.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
thanks I'll give it a shot. but I did reboot recovery, and I'm still unable to see my SD, it still claims it can't mount it.
Also I forgot to include that it is a verizon phone.
dddmcd77 said:
thanks I'll give it a shot. but I did reboot recovery, and I'm still unable to see my SD, it still claims it can't mount it.
Also I forgot to include that it is a verizon phone.
Click to expand...
Click to collapse
Did you flash the correct recovery for the vzw model?
Sent from my Nexus 7 using Tapatalk 4
version
dottat said:
Did you flash the correct recovery for the vzw model?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I attempted to flash the latest nightly file of cm-10.2-20131130-NIGHTLY-m7vzw.zip
dddmcd77 said:
I attempted to flash the latest nightly file of cm-10.2-20131130-NIGHTLY-m7vzw.zip
Click to expand...
Click to collapse
He asked about recovery.
cm-10.2-20131130-NIGHTLY-m7vzw.zip appears to be a ROM?
Oops
carm01 said:
He asked about recovery.
cm-10.2-20131130-NIGHTLY-m7vzw.zip appears to be a ROM?
Click to expand...
Click to collapse
Oh I'm sorry, I read that wrong. My bad. Yes, the recovery worked fine, no issues there.
dddmcd77 said:
Hey guys, I'm new to the HTC one, and I made a mistake. I accidentally formatted my device, the sdcard, firmware, and data, and I'm unable to mount the sdcard and data. I have clockworkmod recovery installed, and the bootloader unlocked, but I'm unable to do much else. When I attempt to flash a rom using sideloader, the screen will just reboot several times. I tried two different roms, CyanogenMod and Stock Rom, by either installing through sideloader or adb, but again, I can't see my SD card. I need help.
How can I fix my phone at this point? I'd be okay with either Stock Rom or CyanogenMod, I just need my phone working.
Please give a newbie a hand guys.
Thanks in advance.
Click to expand...
Click to collapse
Can you walk us through your steps of sideloading? Wondering if you're doing it correctly.
Also, you should reflash the recovery so that you're 100% positive it is for the VZW One.
can do
karn101 said:
Can you walk us through your steps of sideloading? Wondering if you're doing it correctly.
Also, you should reflash the recovery so that you're 100% positive it is for the VZW One.
Click to expand...
Click to collapse
Sure, I boot into recovery and use the command adb sideload "zip file here" and get the loading progess percentage and then it loads on my phone, yet it doesn't work right. Also, for some reason, my phone's bootloader has "relocked" when I know for a fact I avoided that command for fear of ruining my chances to fix the phone, now if I attempt to flash recovery to double check, I'm told its not allowed and it fails.
dddmcd77 said:
Sure, I boot into recovery and use the command adb sideload "zip file here" and get the loading progess percentage and then it loads on my phone, yet it doesn't work right.
Click to expand...
Click to collapse
I'd try a different recovery. Flash TWRP and try it again. If it doesn't work, then I'm out of ideas for you. Last thing I can think about is RUU'ing your phone.
karn101 said:
I'd try a different recovery. Flash TWRP and try it again. If it doesn't work, then I'm out of ideas for you. Last thing I can think about is RUU'ing your phone.
Click to expand...
Click to collapse
Also you can try this method, although i never done it this way
Can Try :
Are you attempting to flash from fastboot or from ruu mode
fastboot oem rebootRUU
fastboot flash zip zipname.zip
fastboot reboot
if it fails try again.
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash romzip.zip
fastboot reboot
Might want to get a full stock ROM here: http://forum.xda-developers.com/showthread.php?t=2485319
I tried RUU
karn101 said:
I'd try a different recovery. Flash TWRP and try it again. If it doesn't work, then I'm out of ideas for you. Last thing I can think about is RUU'ing your phone.
Click to expand...
Click to collapse
I just tried RUUing a few minutes ago, when I attempted to flash stock recovery I was unable, the instructions for VZW told me to flash stock recovery and boot, but I recieved failure notices.
dddmcd77 said:
I just tried RUUing a few minutes ago, when I attempted to flash stock recovery I was unable, the instructions for VZW told me to flash stock recovery and boot, but I recieved failure notices.
Click to expand...
Click to collapse
What firmware you on?
thank you very much
carm01 said:
Also you can try this method, although i never done it this way
Can Try :
Are you attempting to flash from fastboot or from ruu mode
fastboot oem rebootRUU
fastboot flash zip zipname.zip
fastboot reboot
if it fails try again.
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash romzip.zip
fastboot reboot
Might want to get a full stock ROM here: http://forum.xda-developers.com/showthread.php?t=2485319
Click to expand...
Click to collapse
Thanks, I'll give this method a shot right now and report back. my firmware was one of the things that was messed up, and I tried flashing the stock but it was unsucessful.
dddmcd77 said:
Thanks, I'll give this method a shot right now and report back.
Click to expand...
Click to collapse
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot
my firmware
carm01 said:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot
Click to expand...
Click to collapse
To answer your other question, the firmware was one of the many things messed up. Flash attempts of the stock firmware were unsuccessful.
dddmcd77 said:
I just tried RUUing a few minutes ago, when I attempted to flash stock recovery I was unable, the instructions for VZW told me to flash stock recovery and boot, but I recieved failure notices.
Click to expand...
Click to collapse
You don't need to flash the stock recovery.
http://forum.xda-developers.com/showthread.php?t=2475216
The RUU flashes stock recovery. You can skip the first portion (ADB shell) and the last (write secure flag) in the instructions above.
Basically, just start at
fastboot oem rebootRUU
problem with that.
karn101 said:
You don't need to flash the stock recovery.
http://forum.xda-developers.com/showthread.php?t=2475216
The RUU flashes stock recovery. You can skip the first portion (ADB shell) and the last (write secure flag) in the instructions above.
Basically, just start at
fastboot oem rebootRUU
Click to expand...
Click to collapse
My bootloader relocked for some reason. Is that gonna be a problem?
thread closed
hey guys thanks for the help, I just got my phone to stock. Thanks again so much, I owe you all one. You're great people.
dddmcd77 said:
hey guys thanks for the help, I just got my phone to stock. Thanks again so much, I owe you all one. You're great people.
Click to expand...
Click to collapse
What fixed it for you?
Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Just restart device to bootloader, unpack official Lollipop image and run flash-all.bat within directory with fastboot.
It's very difficult to hard brick..
kuba9519 said:
Fastboot works, but adb doesn't see my device now.
Click to expand...
Click to collapse
FWIW adb only works when booted into Android. Fastboot only works in the bootloader.
kuba9519 said:
Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Click to expand...
Click to collapse
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Nexus still in mortal peril
GalaxySN00B:0 said:
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Click to expand...
Click to collapse
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
This shows how to get to recovery mode from the dead Android screen http://www.robschmuecker.com/how-to-boot-into-recovery-mode-nexus-7/
Sent from my XT1080 using XDA Free mobile app
atrielienz said:
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
Click to expand...
Click to collapse
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
DMF1977 said:
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
Click to expand...
Click to collapse
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Use wugs but make sure you tick tablet is in bootloop, worked for me.
atrielienz said:
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Click to expand...
Click to collapse
U can't boot in to android, but u did state earlier that u can boot to the bootloader, and that it was unlocked, so its definitely not hard bricked!