Like the title say I have problem rooting my nexus 7 on Mac.
It's the second one that I have, the first one I got it rooted with techfanatic one click toolkit, but with this one it didn't worked, the only difference that I see is that the one that I have now is on jss15q while when I rooted the other one it was still on jss15j.
So since the one click method haven't worked I tried to do it manually.
I got the latest twrp for flo, the latest super su file and done so:
I navigated in the platform tools, typed ./fastboot OEM unlock selected yes and it unlocked , after I did ./fastboot flash recovery ... and it flashed.
After I pressed start to transfer the super su on my tablet bit it got stuck forever on the x logo.
I tried many times and it didn't worked.
I even tried to wipe data factory reset in twrp but it says failed.
I don't know what to do now, help please.
Sent from my Nexus 4 using xda app-developers app
Does rebooting the bootloader between unlocking and flashing the recovery is necessary, would it make it work?
Sent from my Nexus 4 using xda app-developers app
jonathanxx1 said:
Does rebooting the bootloader between unlocking and flashing the recovery is necessary, would it make it work?
Click to expand...
Click to collapse
For what it's worth, I didn't reboot after unlocking and ended up in a boot loop. Doing a factory reset from (stock) recovery fixed that. Rooting went without problems after that.
jonathanxx1 said:
Like the title say I have problem rooting my nexus 7 on Mac.
It's the second one that I have, the first one I got it rooted with techfanatic one click toolkit, but with this one it didn't worked, the only difference that I see is that the one that I have now is on jss15q while when I rooted the other one it was still on jss15j.
So since the one click method haven't worked I tried to do it manually.
I got the latest twrp for flo, the latest super su file and done so:
I navigated in the platform tools, typed ./fastboot OEM unlock selected yes and it unlocked , after I did ./fastboot flash recovery ... and it flashed.
After I pressed start to transfer the super su on my tablet bit it got stuck forever on the x logo.
I tried many times and it didn't worked.
I even tried to wipe data factory reset in twrp but it says failed.
I don't know what to do now, help please.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
which recovery did you flash? From what I see it should have worked if you used a flo recovery...
mssam said:
which recovery did you flash? From what I see it should have worked if you used a flo recovery...
Click to expand...
Click to collapse
First I flashed twrp for flo 2.6.1 but it ended up in a black screen so I flashed 2.6.0 and it's fine.
BTW I managed to root it.
What I did is I unlocked the bootloader ./fastboot OEM unlock and what I did different is I booted up the tablet , without flashing straight away the recovery.
After the boot I did a quick setup (WiFi and all that) USB debugging on and transfered the super su 1.55 and after I powered off the tablet and booted up on recovery .
In recovery I flashed twrp 2.6.0 , booted up in twrp recovery and there I flashed the super su and boom, rooted.
I will never use a toolkit anymore , the way to go is manually, also you learn how it all work when you do it manually.
Sent from my Nexus 4 using xda app-developers app
jonathanxx1 said:
First I flashed twrp for flo 2.6.1 but it ended up in a black screen so I flashed 2.6.0 and it's fine.
BTW I managed to root it.
What I did is I unlocked the bootloader ./fastboot OEM unlock and what I did different is I booted up the tablet , without flashing straight away the recovery.
After the boot I did a quick setup (WiFi and all that) USB debugging on and transfered the super su 1.55 and after I powered off the tablet and booted up on recovery .
In recovery I flashed twrp 2.6.0 , booted up in twrp recovery and there I flashed the super su and boom, rooted.
I will never use a toolkit anymore , the way to go is manually, also you learn how it all work when you do it manually.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Glad to hear you got it working... :good:
Related
Hi,
I bought the GNexus a month ago, its my 1st android device. (I had a Blackberry for the last 3 years).
I have unlocked my Gnex, and rooted it, then i have installed yakju in order to get rid of my yakjuux ROM, it was my 1st time doing it... Everything worked fine, all my apps were automatically redownloaded and reinstalled from my google account. (Very nice feature).
But for some reason now, I have lost my root acces and I am not sure why or how.. is it normal? I have installed root checker, and supser user returns messages saying he cant get root privileges on my phone.
I tried rooting the phone using superboot. Everyting seemd to have worked fine:
C:\Nexus\r3-galaxynexus-superboot\r3-galaxynexus-superboot>install-superboot-win
dows.bat
C:\Nexus\r3-galaxynexus-superboot\r3-galaxynexus-superboot>fastboot-windows.exe
boot boot.superboot.img
downloading 'boot.img'... OKAY
booting... OKAY
The phone reboted but stayed at the Google logo for like 3 mins. I pulled the battery and after that the phone rebooted normally except superuser cant access root.
Any tips or help is welcome on how to root the phone (already unlocked)
Thanks
You should have left it on there! Mine got stuck on the Google boot logo for around 10 minutes before it was done? I was just about to pull it before it booted up. Go through the process again and give it time
Sent from my Galaxy Nexus using xda premium
Go on YouTube and look for zedomax. He has an easy root video with a link to all the software
Sent from my Galaxy Nexus using xda premium
when you installed the yakju ROM to change yakjuux it deleted root because you fully wiped your phone for a yakju build. just reapply superboot (or install clockwork recovery and flash su.zip that will give you root) and you'll have root.
either that or flash a custom ROM with clockwork recovery and you'll have root.
Another thing is always make a backup of your current favorite rom before flashing anything. I have my original rom and 1 favorite rooted rom on backup at all times. If you do this and encounter problems you can always go in recovery and restore your custom rooted rom. The only reason I keep a stock rom on is in case I have to return the phone. You can remove your unlock symbol by going in fastboot and typing (fastboot OEM lock) I think! This was how I locked my bootloaders back up on my beloved nexus s, good luck and pm me if you need anything
Sent from my Galaxy Nexus using xda premium
zephiK said:
when you installed the yakju ROM to change yakjuux it deleted root because you fully wiped your phone for a yakju build. just reapply superboot (or install clockwork recovery and flash su.zip that will give you root) and you'll have root.
either that or flash a custom ROM with clockwork recovery and you'll have root.
Click to expand...
Click to collapse
Didn't know about su.zip option in CWM, where can I find this zip file for the GNex GSM?
mike216 said:
You should have left it on there! Mine got stuck on the Google boot logo for around 10 minutes before it was done? I was just about to pull it before it booted up. Go through the process again and give it time
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I gave it like 30 mins and still the Google logo was displayed. It seems my rooting did not work properly. Maybe i am not using the right tools?
Zedomax has a nicve procedure, but the link to doenload is GalaxyNexusRoot.zip file is dead. I cant use his method..
Thanks for the help.
gabster21 said:
Didn't know about su.zip option in CWM, where can I find this zip file for the GNex GSM?
Click to expand...
Click to collapse
I couldn't find it on XDA but I did get it off XDA before and have tested it on 4.0.2 when I used 4.0.2 stock. I just uploaded it: http://www.mediafire.com/download.php?4qq8mhu7w0437ky flash in cwr.
md5: 3450886EA845813637419C10DA01BA9D
I was attempting to unlock/root and long story short, now I have TWRP installed, and I can get to FASTBOOT but if i try to boot normally I get the Nexus logo, and no further. When I unlocked, I installed TWRP then loaded it. After leaving TWRP it said 'Seems you are not rooted, want to root"? or something to that effect. I clicked YES and now I'm stuck. Since I had just unlocked it, it *should* have reset my entire device(which was all stock anyway) so I am not sure what went wrong. I have been trying everything I know but I'm now out of ideas. Would appreciate any help. I see now that the version of SuperSu that it would have pushed would have been wrong, would that be preventing the tablet from booting?
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Landara said:
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Click to expand...
Click to collapse
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
I would suggest you just restore your N7 back to stock. No need for root yet, seriously! But this should help get you going in the right direction.
Power it off completely. Hold Power + Volume down until it boots into the bootloader. Run the following commands:
fastboot devices (to confirm you are connected)
fastboot flash recovery recovery.img
If you haven't unlocked your N7 yet, run fastboot oem unlock first.
ronni.rasmussen said:
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Landara said:
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Click to expand...
Click to collapse
Start over by downloading recovery, Superuser and a clean stock rom image.
But before that you could try to reset all data in recovery (factory reset) and cache if you haven't tried.
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Landara said:
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Click to expand...
Click to collapse
Super
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
So I just picked up this device couple days ago. It's running 4.4.2
This has surely been asked before but how do I root this build? I only found TUTs for 4.3 here on xda
Thanks
PS. This is my first nexus device
//Sent from somewhere in your house
Wug's Nexus Root Toolkit v1.8.2
http://forum.xda-developers.com/showthread.php?t=2389107
lzzar said:
So I just picked up this device couple days ago. It's running 4.4.2
This has surely been asked before but how do I root this build? I only found TUTs for 4.3 here on xda
Thanks
PS. This is my first nexus device
//Sent from somewhere in your house
Click to expand...
Click to collapse
Fastboot commands to unlock bootloader and install TWRP. Then flash a root zip.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
Fastboot commands to unlock bootloader and install TWRP. Then flash a root zip.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which command is to unlock the bootloader?
//Sent from somewhere in your house
lzzar said:
Which command is to unlock the bootloader?
//Sent from somewhere in your house
Click to expand...
Click to collapse
fastboot oem unlock
okay so I unlocked the bootloader and flashed recovery. I can boot normally but not into recovery. it gives me the android with the red triangle.
I know the BL is unlocked cause I see the lock symbol at the Google screen
I tried both cwm and twrp
Help?
lzzar said:
okay so I unlocked the bootloader and flashed recovery. I can boot normally but not into recovery. it gives me the android with the red triangle.
I know the BL is unlocked cause I see the lock symbol at the Google screen
I tried both cwm and twrp
Help?
Click to expand...
Click to collapse
It sounds like you still have the stock recovery installed instead of the custom one you're trying to flash. What command are you using to flash the custom recovery? It should be:
fastboot flash recovery [insert recovery filename here].img
Then, use the volume buttons to boot into recovery from the bootloader. Your custom recovery should boot up.
Yeah I used that command. I have used it before on my Optimus 3D
//Sent from somewhere in your house
lzzar said:
Yeah I used that command. I have used it before on my Optimus 3D
//Sent from somewhere in your house
Click to expand...
Click to collapse
Are you using the proper TWRP? You may try the command again.
Edit: In order to flash you have to CD from a folder containing adb.exe and fastboot.exe. Otherwise nothing will flash. Download this folder https://docs.google.com/file/d/0B_nizg6yUZ0NbWNvZHFMR1h6LVE/preview?pli=1 and Stick TWRP in the folder. That folder was put together by Rootjunky.com http://m.youtube.com/watch?v=6k4rCaMPSQ8
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Nevermind guys, I got it working! !
Changed a little stuff (usb port and cable, wiped data before flashing)
//Sent from somewhere in your house
@lzzar Glad you got it figured out.
Short story for anyone who might find this thread after seeing the Red Triangle.
I saw an article on Android Police that there was 32gb refurbs for sale for $170. So, clearly we (XDA members) are not the same as normal users when it comes to troubleshooting and fixing problems. So, I bought my 2 sons 1 each and my wife 1 as well. While my sons are very young (single digit ages), I've taught them how to run code. The N7's arrived yesterday and after they went to bed, I fired up the computer and had all 3 tabs going at once updating from 4.3 to 4.4.2, charging, downloading,....
Unlocked all 3 Bl's and proceeded to install TWRP and ROM/Kernels. Point to remember is that I had too many things going on at once. On the very first recovery.img flash, I got the laying down android with red triangle. Flashed the recovery.img again and again the red triangle, all the while I was downloading ROMs and Kernels on my PC.
Then I realized what I was doing wrong. After flashing the recovery.img, I booted into the OS, then powered off and used the key combo to boot into recovery. Wrong!! What step did I miss? After flashing fastboot flash recovery recovery.img, I had forgotten to Volume up and boot into recovery from straight from there.
Once I realized my blunder, I was much happier. After that, it took me under an hour to install recoveries on all 3, flash ROMs and Franco r13, boot and reflashed SuperSU. Too many things going on at once and maybe a few too many drinks as well.
Yes, the exact same mistake with booting into OS after flashing was what I did too
//Sent from somewhere in your house
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Flashing back to stock is a first step, to ensure it's nothing in the software. What do you mean by "So far no success"?
Use Wugfresh's Nexus Root Toolkit. There is a option named Stock Flash+Unroot (Bootloop). The device should be able to get into fastboot mode, though.
aniket0317 said:
Use Wugfresh's Nexus Root Toolkit.
Click to expand...
Click to collapse
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
mistermabuse said:
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
Click to expand...
Click to collapse
Press thanks if I helped you
Sent from my Nexus 7 using Tapatalk
Same problem
Hey,
my Nexus 7 2013 has the same error.
Im stuck in Google screen, only enter in fastboot mode.
Tried Nexus Root Toolkit and other methods but stays the same...
In TWRP, touchscreen doesnt work.
What can i do???
Thanks!
Hey thiago,
I don't really know what to do, but I have the same problem now...
I guess it should be possible to somehow boot clockworkmod recovery from fastboot,
but I'm not sure.
I'll mark this thread not solved again -.-
mistermabuse said:
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Click to expand...
Click to collapse
EDIT 2: Yes it worked, at first. Now the device is stuck in a bootloop again. I can boot into team win recovery, but touch doesn't work there so I can't do anything. Booting CWM from fastboot is also not suceessful.
What do you mean CWM is not successful, that there's no touch response? If all else fails, you can use the non-touch version of CWM, using the side buttons to navigate. But I'd be concerned if screen touches are not being recognized.
CWM dont start. Only twrp. Is there a TWRP non touch version?
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
6.0.4.3 for regular N7 2013: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-flo.img
6.0.4.8 for N7 2013 LTE: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-deb.img
6.0.4.3 for N7 2013 GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-tilapia.img
still frozen
Pandae said:
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
[/url]
Click to expand...
Click to collapse
Yes, i used this version for Regular N7 2013, but still frozen in the google screen.
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Sent from my SM-G900F using XDA Premium HD app
Send it back to Google
gopin said:
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Click to expand...
Click to collapse
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Pandae said:
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes. I flashed the factory images using wugs nexus toolkit and ticked the option flash stuck + unroot (bricked or bootlooping) to see if it would work as mentioned by OP. All factory images flash successfully all partitions, but it does not boot recovery or system. I tried different android versions hoping it would make a difference and tried booting recovery after flashing each image (4.4.4 and 4.3). I haven't tried typing the command flash all.bat myself to flash the image as you suggested. I've used the toolkit to make it easier. I'll try flashing stock typing command flash all.bat myself and report.
Sent from my SM-G900F using XDA Premium HD app
Use your warranty, send it back to Google.