Related
I tried to root my new nexus s that i got last friday.....
tey must be some thread about this but my english is not in top shape...
i am now stuck at google page when turning on my phone. must be something about my boot....
I live in Canada and my provider is roger here all the information that i found :
in fastboot mode:
product name: herring
hw version : rev 16
bootloader version : i9020xxka3
baseband version : i9020uckb2
carrier info : att
on my box:
model: gt-i9020fsrrwc
Please i realy need help.....
Vbob
Describe steps you have taken to root in detail.
i know this is not the right place to start, but i did't know....
hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
i was stock after "fastboot flash boot rootboot.img" i was ubable to reboot
Vbob
any one can help me?
Vbob
Download this first
http://www.mediafire.com/?0pzz830oc0xa0e7
Rename it to rootboot.img and overwrite the one in C:\nexusroot
Try
Code:
fastboot flash boot rootboot.img
again.
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
vbobmac said:
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
Click to expand...
Click to collapse
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
redlilcivic said:
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
Click to expand...
Click to collapse
You need to describe the steps you have taken, and describe the problem with more detail.
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
Click to expand...
Click to collapse
i did a update yesterday, and now i think i dont have the right system recovery.
now when clicking system recovery, i get a "!" whit the android character...
vbobmac said:
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
Click to expand...
Click to collapse
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
[email protected]_OC said:
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
Click to expand...
Click to collapse
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
reddv1 said:
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
[email protected]_OC said:
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
Click to expand...
Click to collapse
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
reddv1 said:
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes, i can mount my phone, but when i try to install the default rom, but it's not working. I have an error.
At least the manipulation is working, i can mount on my computer the nexus.
Do you have a rom 2.3.4 for Nexus i9023 please? Maybe i don't flash with a good rom?
Thanks again for your help.
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
[email protected]_OC said:
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
Click to expand...
Click to collapse
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
reddv1 said:
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
And I think, i don't have the good bootloader.
My phone is a Nexus S i9023, but since i try to root my phone, my bootloader version is the "i9020XXKA3".
You think, i have to change the bootloader first?
For flashing bootloader and clocwork recovery, i have to do it from Windows?
Waiting for your answer.
Thank's a lot
[email protected]_OC said:
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
Click to expand...
Click to collapse
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
reddv1 said:
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash the recovery, and now i have the v4.0.0.2, but i still can't flash a rom.
I still have the same message:
"assert failed: file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.2/GRH78C/93600:user/release-keys" ||
file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.3/GRI40/102588:user/release-keys"
E: Error in /sdcard/update 2.3.3.zip
(Statut 7)
Installation aborted.
Don't you think it's because my bootloader is not the good one?
Can flash it too, from Windows?
Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).
aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.
You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app
try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688
Okay, thanks guys. I'm on it. Will let you know when I'm done.
That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:
Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!
i tried installing a system font from the rom toolbox and when it rebboted it wasnt booting up... i can switch on my device but it remains in the glowing (X) and doesnt load up... i tried a factory reset i didnt work... i dont have a custom recovery nor do i have a nandroid backup on my device. i have rooted it using wugfresh's toolkit.
i have been trying many methods over the day and nothing seems to work. i have dowloaded a stock image from google's site but its on my pc. some help pls!!!!
i have the drivers installed on my windows 8 . atleast they were wokring intially when i got the root done on it . i have no clue what to do now !!
Your gonna have to flash the stock image from download mode. Never make changes to system files without doing a nandroid backup.
Wayne Tech Nexus
zelendel said:
Your gonna have to flash the stock image from download mode. Never make changes to system files without doing a nandroid backup.
Wayne Tech Nexus
Click to expand...
Click to collapse
i am sorry but i am new to nexus 4 ... how do i get into the download mode?
Irthu said:
i am sorry but i am new to nexus 4 ... how do i get into the download mode?
Click to expand...
Click to collapse
Read the stickies. They will get you all the info you need. If you are gonna try mods like this I would advise a full custom set up. As what your gonna do is gonna fully wipe your device.
Wayne Tech Nexus
zelendel said:
Read the stickies. They will get you all the info you need. If you are gonna try mods like this I would advise a full custom set up. As what your gonna do is gonna fully wipe your device.
Wayne Tech Nexus
Click to expand...
Click to collapse
is it possible to flash the img. file if my phone is recognised only in the bootloader mode? and i am assuming we have to flash the img. file using an adb software ?
Irthu said:
is it possible to flash the img. file if my phone is recognised only in the bootloader mode? and i am assuming we have to flash the img. file using an adb software ?
Click to expand...
Click to collapse
yes you will need to use fastboot which is part of adb
follow this thread: http://forum.xda-developers.com/showthread.php?t=2010312
PhantomGamers said:
yes you will need to use fastboot which is part of adb
follow this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
i have downloaded a zip from google's site and its about 300 odd mb. i am assuming i have to extract the the img. files and then do it ? but there are about 3-4 img. files such as :
system
boot
boot loader
radio
recovery
user data
since my phone does get into bootloader can u pls tell me which all img. files i need to flash? do i have to everyone of them?
the thread i linked answers all of your questions
(you really only need to flash the system image but to avoid confusion i would just follow the thread verbatim)
PhantomGamers said:
the thread i linked answers all of your questions
(you really only need to flash the system image but to avoid confusion i would just follow the thread verbatim)
Click to expand...
Click to collapse
thanks alot i will try doing it... i havent used the command prompt in windows ever before guess its time to learn how to do this..
hello everyone..
In serious need of help here and hope someone can help..
Due to the massive battery drain issue I have been having, I tried to flash the original stock rom on my nexus 7 and
things have gone downhill really bad..
in the past, I flashed using this guide (http://forum.xda-developers.com/showthread.php?t=1907796)
without any problems but last night.. I encountered errors when trying to flash the bootloader
and radio IMG files.. neeedless to say when it comes to flashing the rom in, it came out with errors and my nexus remain OS-less
the errors when trying to flash the bootloader and radio are
"failed (command write failed (Invalid Argument))"
can anyone help me?
p.s :- if anyone can even suggest me a easier way to flash custom roms in and so forth, your suggestion will be most welcomed..
also, I did try wug's rootkit plus the nexus 7 toolkit or something, both came out errors too when too do any flashing in relating to
the bootloader or system.. thanks
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Username invalid said:
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Click to expand...
Click to collapse
actually, my bootloader boots fine, it shows tilapia 4.18.
so does this mean I dont have to flash it?
if I dont have to flash the bootloader, do I have to flash the radio?
sorry, kind of a noob in these things..
Anyway, is it normal for the bootloader flash attempt to fail?
hamiksu said:
Anyway, is it normal for the bootloader flash attempt to fail?
Click to expand...
Click to collapse
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
korockinout13 said:
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
Click to expand...
Click to collapse
hmm, ok..
then I will go back home and do the system flashing and try and post out the errors it stated there..
really hope to get my nexus back on line...
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
hamiksu said:
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
Click to expand...
Click to collapse
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
it says my bootloader is already unlocked
hamiksu said:
it says my bootloader is already unlocked
Click to expand...
Click to collapse
Then it sounds like something happened to your system partition that should not have happened.
Are you sure the system image you're trying to flash is valid, do the md5 sums match?
How about flashing another system image?
Or flash a custom recovery, and install a new ROM from there?
ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
ameinild said:
Then it sounds like something happened to your system partition that should not have happened. Sorry, can't help you there...
Click to expand...
Click to collapse
meaning my system partition is screwed?
anyone knows how to go around this problem?
p.s :- anyway ameinild, thanks for trying to help
hamiksu said:
p.s :- anyway ameinild, thanks for trying to help
Click to expand...
Click to collapse
I edited my post with some more suggestions to try first
ameinild said:
I edited my post with some more suggestions to try first
Click to expand...
Click to collapse
yup, the image i tried a few.. even tried stock rom image.
tried both nexus 7 toolkit
as well as wugs nexus root tool kit.
they all seem to encounter problems when trying to "push" the rom images in or something.
is there a way to like format the entire thing and install from scratch>?
hamiksu said:
is there a way to like format the entire thing and install from scratch>?
Click to expand...
Click to collapse
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
ameinild said:
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
Click to expand...
Click to collapse
Yea, I hope someone will pop in and be my guardian angel too..
Thanks again, Ameinild
tried to flash stock rom using wug's rootkit..
this is what happens...
hamiksu said:
tried to flash stock rom using wug's rootkit..
this is what happens...
Click to expand...
Click to collapse
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Rirere said:
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Click to expand...
Click to collapse
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
I'm assuming you haven't tried this yet, if you have tried this just ignore.
1 - Download - http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.0.0-grouper.img
2 - fastboot flash recovery openrecovery-twrp-2.6.0.0-grouper.img
If flashes fine:
Power off Nexus, Hold Volume down and Power on, keep holding power down until you get to recovery.
Then:
Either - Get a USB OTG and put a ROM on a USB Stick, go to "install" - "Use external storage" find the rom and flash it.
or
Plug in to PC whilst in recovery, - Mount Storage - Now the Nexus should pop up on PC, Drag ROM to Nexus. Unmount and then try to flash.
Let me know how you get on with this.
Regards.
hamiksu said:
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
Click to expand...
Click to collapse
That's because you have stock recovery installed now and it's unable to verify that your device is in working order, hence the red mark. Find TWRP for your device, download the .img and try to flash it with fastboot flash recovery <path-to-recovery.img>. Since you can at least get into a recovery, it's possible you'll be able to use onboard recovery tools to see what state your internal partitions are in.
Until there's a little more info available, there's nothing I can say that's not pure conjecture.
I was restoring a twrp backup and when it reaches "flashing system image" in the restore process it just reboots. Ive tried a few things but cant get it going. It just bootloops.
dontbeweakvato said:
I was restoring a twrp backup and when it reaches "flashing system image" in the restore process it just reboots. Ive tried a few things but cant get it going. It just bootloops.
Click to expand...
Click to collapse
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Heisenberg said:
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Click to expand...
Click to collapse
That was my first rooted twrp backup on 6p. I checked everything under what to backup. It has a system and system image to backup along with everything else. I thought it was weird to have both of them because I've never seen that before in twrp.
Well im back to normal. I must of screwed up the restore with the "system" and "system image" business. What's the difference in twrp restore between the two?
dontbeweakvato said:
Well im back to normal. I must of screwed up the restore with the "system" and "system image" business. What's the difference in twrp restore between the two?
Click to expand...
Click to collapse
Honestly, I don't know. I only know that you only need to backup system, boot, and data (if you want your apps and settings).
Heisenberg said:
Flash the factory images with fastboot, see section 9 of my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Did you actually backup "system image" or just "system"? It should be only system, not the system image.
Click to expand...
Click to collapse
I have a soft bricked phone... I have done everything in your thread and flashing all the files worked except i get an error when flashing the system.img
it says error unable to allocate xxxxxxx bytes...? i really want my phone back to normal.. PLEAS HELP
taylorleach said:
I have a soft bricked phone... I have done everything in your thread and flashing all the files worked except i get an error when flashing the system.img
it says error unable to allocate xxxxxxx bytes...? i really want my phone back to normal.. PLEAS HELP
Click to expand...
Click to collapse
Try to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files.
indian84 said:
Try to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files.
Click to expand...
Click to collapse
I am sorry what do you mean?? what commands should I try?
taylorleach said:
I am sorry what do you mean?? what commands should I try?
Click to expand...
Click to collapse
Try this.
Reboot Bootloader again
1. fastboot erase userdata
And then follow the guide. Hopefully this will help.
indian84 said:
Try this.
Reboot Bootloader again
1. fastboot erase userdata
And then follow the guide. Hopefully this will help.
Click to expand...
Click to collapse
so, just to clarify... run the command "fastboot erase userdata" then run all of the IMG files?
taylorleach said:
so, just to clarify... run the command "fastboot erase userdata" then run all of the IMG files?
Click to expand...
Click to collapse
My bad.
use command fastboot format userdata
This will erase everything on your phone. Including photos and all the media.
After this use below command
fastboot reboot bootloader
And then follow guide and flash all IMG files.
indian84 said:
My bad.
use command fastboot format userdata
This will erase everything on your phone. Including photos and all the media.
After this use below command
fastboot reboot bootloader
And then follow guide and flash all IMG files.
Click to expand...
Click to collapse
that did not work same problem
"load_file: could not allocate 2014315040 bytes
error: cannot load 'C:\angler\images\system.img"
all other .img files i get OKAY except for system.img
PLEASE HELP ME UGG I REALLY NEED MY PHONE TO WORK AGAIN. I even tried re downloading the 6.0.1 again and also tried rebooting PC and multiple USB ports...
taylorleach said:
that did not work same problem
"load_file: could not allocate 2014315040 bytes
error: cannot load 'C:\angler\images\system.img"
all other .img files i get OKAY except for system.img
PLEASE HELP ME UGG I REALLY NEED MY PHONE TO WORK AGAIN. I even tried re downloading the 6.0.1 again and also tried rebooting PC and multiple USB ports...
Click to expand...
Click to collapse
You need to update your fastboot on your PC update everything in Android SDK or install latest minimal adb and fastboot. The system needs to be sent/flashed in parts as it's a big file. That will/should fix your issue.
matt1515 said:
You need to update your fastboot on your PC update everything in Android SDK or install latest minimal adb and fastboot. The system needs to be sent/flashed in parts as it's a big file. That will/should fix your issue.
Click to expand...
Click to collapse
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
taylorleach said:
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
Click to expand...
Click to collapse
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
taylorleach said:
I really appreciate your reply.. But i am a bit new to the Nexus and fastboot (sdk) environment. How do I update fastboot? I believe I have updated my Android Studio properly already. Is there a way to flash that system.img in stages then? I am so confused. Thanks again in advance!!!
Click to expand...
Click to collapse
matt1515 said:
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
Click to expand...
Click to collapse
If you already have the Android SDK it probably isn't a good idea to start installing other versions. Just go to where you installed the SDK on your PC, open SDK Manager, and update the platform-tools package.
matt1515 said:
Assuming you have Windows go to this site and download latest version(1.31) https://androidmtk.com/download-minimal-adb-and-fastboot-tool
Read Heisenberg's thread on how to flash everything but put all your files(system, boot, bootloader, radio, boot, vendor, cache, userdata in the minimal adb and fastboot folder hold shift right click and open cmd window and flash away it will work follow Heisenberg's thread and you should be good! Good luck!
Click to expand...
Click to collapse
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
taylorleach said:
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
Click to expand...
Click to collapse
Yes that's why it was stuck in a boot loop, the version of SuperSU that's included in TWRP is incompatible. Which version of TWRP did you flash? You need the latest in order for it to be able to successfully decrypt your storage so you can view it.
Heisenberg said:
Yes that's why it was stuck in a boot loop, the version of SuperSU that's included in TWRP is incompatible. Which version of TWRP did you flash? You need the latest in order for it to be able to successfully decrypt your storage so you can view it.
Click to expand...
Click to collapse
To be honest, I moved the file to my phones directory from my PC and did not just copy it so I lost it lol. Could you please tell me what one I should flash so I don't mess anything up. PLEASE and THANK YOU
taylorleach said:
YOUR ARE MY BEST FRIEND THANK YOU SO MUCH!! I knew I was close to figuring it out but I seriously appreciate your help good sir.
So, to ask one more question. I flashed TWRP totally fine, but when I when to reboot after failing to find my SU.zip in my phones directory (due to 0MB detected.. i don't know why) it asked me if I wanted to root because I was currently not rooted and I just said yes.. was that why it got stuck in a bootloop? I never actually directed it at my specific SU.zip file because it wouldn't appear in the phones files?
Click to expand...
Click to collapse
+1 on Heisenberg you should use Android SDK and update properly but I knew you needed to get back up and running and figured that was the fastest way to help you. Read his thread like you would a book you will learn all you need to learn! But glad to hear I was able to help! Always use latest TWRP and SuperSU and you will be fine if you can decrypt then install SuperSU that way if not just hit cancel and adb sideload it. Look in general thread for the TWRP thread. Good luck and enjoy your working phone again!