My nexus 6 is soft bricked I'm assuming, I can't get past the 6.0.1 boot up screen it just keeps on booting . The device is unlocked with TWRP recovery but not rooted as far as I know it's not rooted. The only way I can check MTP is through twrp but it's showing an exclmation point in device mgr. I'm in wugs toolkit now under Advanced Utilities, before I got the boot logo it had the you're device is corrupt. I fixed the corrupt message by putting my device in boot loader mode and in Advanced Utilities under fastboot flash then I clicked Boot [Kernel] I flashed the stock kernel and that got rid of the corrupt device warning screen. I'm gonna try flashing a modified boot img next but I'm having trouble. I just need someone to stick with me for awhile and help me fix this thing because I gotta return it and I don't have long.
Sent from my HTC6600LVW using Tapatalk
Ok now I have the corrupt device message back again.
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
My nexus 6 is soft bricked I'm assuming, I can't get past the 6.0.1 boot up screen it just keeps on booting . The device is unlocked with TWRP recovery but not rooted as far as I know it's not rooted. The only way I can check MTP is through twrp but it's showing an exclmation point in device mgr. I'm in wugs toolkit now under Advanced Utilities, before I got the boot logo it had the you're device is corrupt. I fixed the corrupt message by putting my device in boot loader mode and in Advanced Utilities under fastboot flash then I clicked Boot [Kernel] I flashed the stock kernel and that got rid of the corrupt device warning screen. I'm gonna try flashing a modified boot img next but I'm having trouble. I just need someone to stick with me for awhile and help me fix this thing because I gotta return it and I don't have long.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
If TWRP is installed there's no problem. Just a matter of the pc let recognize the device. Quit the toolkits though!
Do you have google drivers installed? Once they are installed your device should be recognized and you can copy any of the fine roms that can be found here.
Droidphilev said:
If TWRP is installed there's no problem. Just a matter of the pc let recognize the device. Quit the toolkits though!
Do you have google drivers installed? Once they are installed your device should be recognized and you can copy any of the fine roms that can be found here.
Click to expand...
Click to collapse
I need a lot of help installing the drivers.
Sent from my HTC6600LVW using Tapatalk
Like I said I now have the corrupt device message back instead of the 6.0.1 boot logo. I tried flashing the stock img file and the stupid corrupt screen came back. Ok I'm just craps out luck I guess,
Sent from my HTC6600LVW using Tapatalk
Ok I have what says is the latest Google usb drivers which was Aug 2015 downloaded. On my device I'm using I'm gonna transfers the drivers to my pc now, and attempt to install them. I hope this works and fixes my device. I sat in front of my pc yesterday for 7 hrs trying to fix this stupid phone.
Sent from my HTC6600LVW using Tapatalk
the corrupt device message is only there because you have twrp and a stock kernel. flash a custom kernel.
It's fixed, everything is running as it should no boot loops or corrupt screen, now I gotta check to see if recovery is gone. I used wugs to flash stock 6.0.1
Sent from my HTC6600LVW using Tapatalk
I used to have the corrupt message also, but it would go away and boot just fine. Started when I had TWRP. As someone mentioned, if this is a really annoyance, just flash a custom kernel . Though mine went away when I rooted with SuperSU (which patches the kernel I think)
Tower1972 said:
I used to have the corrupt message also, but it would go away and boot just fine. Started when I had TWRP. As someone mentioned, if this is a really annoyance, just flash a custom kernel . Though mine went away when I rooted with SuperSU (which patches the kernel I think)
Click to expand...
Click to collapse
I used wugs toolkit to flash back to complete stock it worked my device is running as normal, but when I power of the device and power it back on the corrupt message then disappears and boots right up. When I boot into boot loader mode and boot recovery it shows the green android robot laying down. After I flashed back to stock 6.0.1 it got rid of twrp and root but I'm still unlocked . The unlocked part I'm not worried about. In order to fix this do I have to 're root and flash twrp all over again or is there an easier way. I need step by step, on how to get rid of the corrupt message. Example, like when someone says flash img to me that's about as clear as mud.....
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I used wugs toolkit to flash back to complete stock it worked my device is running as normal, but when I power of the device and power it back on the corrupt message then disappears and boots right up. When I boot into boot loader mode and boot recovery it shows the green android robot laying down. After I flashed back to stock 6.0.1 it got rid of twrp and root but I'm still unlocked . The unlocked part I'm not worried about. In order to fix this do I have to 're root and flash twrp all over again or is there an easier way. I need step by step, on how to get rid of the corrupt message. Example, like when someone says flash img to me that's about as clear as mud.....
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
flash twrp then when you root, flash a custom kernel as well, that will get rid of the message.
Anybody here?
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
Anybody here?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
me. well not here, but in nyc. here in spirit though
simms22 said:
me. well not here, but in nyc. here in spirit though
Click to expand...
Click to collapse
I'm trying to get my brain working,lol my device is stock unrooted without twrp but the corrupt message still shows up I gotta get this fixxed. It's hard for me to understand what all I need to do. All I need is the corrupt message to go away and I'll be good. At start up it shows the corrupt message, but a few seconds later it goes away and it boots up normally.
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I'm trying to get my brain working,lol my device is stock unrooted without twrp but the corrupt message still shows up I gotta get this fixxed. It's hard for me to understand what all I need to do. All I need is the corrupt message to go away and I'll be good. At start up it shows the corrupt message, but a few seconds later it goes away and it boots up normally.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
i believe that your bootloader is unlocked, thats why its showing up on a non rooted n6. you can lock your bootloader(i wouldnt, you can have problems later) or you can flash twrp recovery, then a custom kernel, and you dont need to root it for that.
simms22 said:
i believe that your bootloader is unlocked, thats why its showing up on a non rooted n6. you can lock your bootloader(i wouldnt, you can have problems later) or you can flash twrp recovery, then a custom kernel, and you dont need to root it for that.
Click to expand...
Click to collapse
If I flash the kernel with twrp it's gotta be a zip? Is there anyway that you can link me to stock 6.0.1 kernel
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
If I flash the kernel with twrp it's gotta be a zip? Is there anyway that you can link me to stock 6.0.1 kernel
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
a stock twrp flashable, then theres no zip version of it available. BUT twrp can also flash .img kernels as well. if you have the factory image available, you can unzip it and just flash the boot.img in twrp(or fastboot). but why the stock kernel?? if you just want stock, id recommend just fastboot flashing the boot.img from the factory image. boot.img is the kernel.
simms22 said:
a stock twrp flashable, then theres no zip version of it available. BUT twrp can also flash .img kernels as well. if you have the factory image available, you can unzip it and just flash the boot.img in twrp(or fastboot). but why the stock kernel?? if you just want stock, id recommend just fastboot flashing the boot.img from the factory image. boot.img is the kernel.
Click to expand...
Click to collapse
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
nope. the kernel is what connects the operating system(software) to the hardware and also serves as the devices main "brain"
---------- Post added at 05:10 PM ---------- Previous post was at 05:08 PM ----------
mwebb34 said:
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
just download the factory image, then grab the boot.img out of it. link to the 6.0.1 factory image https://dl.google.com/dl/android/aosp/shamu-mmb29k-factory-9a76896b.tgz
simms22 said:
nope. the kernel is what connects the operating system(software) to the hardware and also serves as the devices main "brain"
Click to expand...
Click to collapse
Ok, with no twrp recover when I boot into boot loader mode and then boot into recovery mode what should I see come up on the screen?
Sent from my HTC6600LVW using Tapatalk
Related
Guys I need your help please..I root the tablet and flash Cromix ROM but the speaker went to crap..lots of crackling and distorted noise. So I went into recovery and flashed jb-4.3_ota-full_tf701t-macallan.zip to go back to stock. It did but its unstable and the speaker is still horrible..So I tried going to Asus Web site and DL the UL-K00C-WW-10.26.1.18-user.zip and put it in my Sd card and rebooted the device chosing RCK and it gives me an error..also did a wipe data on the option by the RCK...I cannot get it back to factory stock..what did I do wrong?
About in the settings
Build number
JSS15J.US_epad-10.26.1.18-20131217
020115_2013102100002
Then in Recovery is the Macalla-user BL released by "Us_epad-10.26.1.7-20131108"
I don't want to send it back to Asus, they are gonna charge me to fix this problem..Thanks
anyone please have any idea?
At least on tf201 (ordered my tf701 today) flashing stock rom downloaded straight from asus is a big no no on unlocked bootloader. You wiped data in rck? Do you mean in recovery or in the menu where are rck, fastboot and wipe data (just making sure)
How about in what state is your tablet now?
Sent from my LG D802
pachi72 said:
anyone please have any idea?
Click to expand...
Click to collapse
You can try this:
Download the stock recovery from here: http://droidbasement.com/db-blog/?p=3210
Copy the image to your fastboot folder.
Download the Asus firmware, unzip the file once and copy it to your internal SD.
Boot tablet into fastboot
Issue this command
Code:
fastboot boot recovery.img
Note: Do not flash the recovery, just boot it.
It should recognize the firmware file on your tablet and flash it.
BTW, I doubt the rom has anything to do with your speaker problem, but it would be interesting to find out. Please report back.
berndblb said:
You can try this:
Download the stock recovery from here: http://droidbasement.com/db-blog/?p=3210
Copy the image to your fastboot folder.
Download the Asus firmware, unzip the file once and copy it to your internal SD.
Boot tablet into fastboot
Issue this command
Code:
fastboot boot recovery.img
Note: Do not flash the recovery, just boot it.
It should recognize the firmware file on your tablet and flash it.
BTW, I doubt the rom has anything to do with your speaker problem, but it would be interesting to find out. Please report back.
Click to expand...
Click to collapse
I tried and it would give me an error
Sent from my HTC One_M8 using Tapatalk
I tried and it would give me an error.
Sent from my HTC One_M8 using Tapatalk
pachi72 said:
I tried and it would give me an error
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
What error?
berndblb said:
What error?
Click to expand...
Click to collapse
When I tried to flash the recovery image.
Sent from my HTC One_M8 using Tapatalk
YOU DO NOT FLASH THE RECOVERY IMAGE!
Boot it. Read the post and command.
You basically sideload the recovery. Instead of flashing it to your device, you boot it from your PC. But it should still function as if installed.
If you get an error, write it down. Exactly as it reports it.
Sent from my K00C using Tapatalk
Right, so I've been following http://forum.xda-developers.com/xperia-z/orig-development/root-xperia-z-c660x-unlocked-t2154310 to root my xperia z. I followed the instructions but when I wrote the second image it refused to boot properly, looping constantly through the sony logo IIRC.
To fix this I used the recovery image. I can get into it just fine but when I try to install SuperSU-1.25-Busybox-1.20.2-UPDATE.zip it goes through the motions, but rebooting the phone just brings me back into recovery mode. Any ideas on what's wrong?
Rare Devil said:
Right, so I've been following http://forum.xda-developers.com/xperia-z/orig-development/root-xperia-z-c660x-unlocked-t2154310 to root my xperia z. I followed the instructions but when I wrote the second image it refused to boot properly, looping constantly through the sony logo IIRC.
To fix this I used the recovery image. I can get into it just fine but when I try to install SuperSU-1.25-Busybox-1.20.2-UPDATE.zip it goes through the motions, but rebooting the phone just brings me back into recovery mode. Any ideas on what's wrong?
Click to expand...
Click to collapse
there is only one image that you need to flash that is boot.img
after that flash advance stock kernel in recovery followed by super su make sure your bootloader is unlocked if you plan to flash custom kernel
what firmware you are on?
Unlocking bootloader invalidates warranty
androidtweaker1 said:
there is only one image that you need to flash that is boot.img
after that flash advance stock kernel in recovery followed by super su make sure your bootloader is unlocked if you plan to flash custom kernel
what firmware you are on?
Unlocking bootloader invalidates warranty
Click to expand...
Click to collapse
I'm not sure what firmware I'm on but I did update it just before I tried all this. I did unlock my bootloader and used boot.img to get into recovery mode. Super su is done through recovery mode right? Because every time I try to install it it just returns to recovery mode with no changes
Rare Devil said:
I'm not sure what firmware I'm on but I did update it just before I tried all this. I did unlock my bootloader and used boot.img to get into recovery mode. Super su is done through recovery mode right? Because every time I try to install it it just returns to recovery mode with no changes
Click to expand...
Click to collapse
Try twrp recovery you can download the .img from here
after flashing recovery try flashing SU from twrp.
post the results
androidtweaker1 said:
Try twrp recovery you can download the .img from
after flashing recovery try flashing SU from twrp.
post the results
Click to expand...
Click to collapse
Flashing that img gives me an error "writing: 'recovery' FAILED (remote: Command not allowed)
If you want to try TWRP, try Dual Boot recovery with Philz Touch CWM Advanced Edition and TWRP by shoey63.
Sent from my C6603 using Tapatalk
What do I specifcally type for that? From what I've seen different img files use different commands
Rare Devil said:
What do I specifcally type for that? From what I've seen different img files use different commands
Click to expand...
Click to collapse
fastboot flash boot boot.img
By the way, the guide you were following is outdated and has an old version of the kernel, that's why you went into a bootloop.
Sent from my C6603 using Tapatalk
kingvortex said:
fastboot flash boot boot.img
By the way, the guide you were following is outdated and has an old version of the kernel, that's why you went into a bootloop.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
It booted properly. Thanks. So from there it's just installing zip? Or are there any other steps?
Flash a SuperSu zip and you're rooted. Simple as that.
I suggest this one - SuperSU zip.
Sent from my C6603 using Tapatalk
kingvortex said:
Flash a SuperSu zip and you're rooted. Simple as that.
I suggest this one -
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
It still gives me a black screen when I reboot and go past the sony startup screen. How long does it usually take?
Rare Devil said:
It still gives me a black screen when I reboot and go past the sony startup screen. How long does it usually take?
Click to expand...
Click to collapse
http://d-h.st/UP0
this help me, but back me to KK 4.4.4, but i have my sony back
Hello everyone. I have rooted the G4, have SuperSU, and was going about installing TWRP. I used flashify and the TWRP version made for the H811 contained in these forums. Flashify seemed to install image correctly, but upon rebooting into recovery, I got a "Secure Boot Error 1003" and then a reboot to normal operation. I have searched and seen fixes for different devices, but none for the G4. Where did I go wrong and what can I do now?
Did you hit flash boot img in flashify instead of recovery img? You could try to boot into download mode and redo root process should fix then flash twrp using flash recovery img in flashify.
Sent from my LG-H811 using Tapatalk
---------- Post added at 05:29 PM ---------- Previous post was at 05:24 PM ----------
If redoing the root process doesn't fix you can try using the kdz file to return to stock, then re root and re flash twrp in flashify.
Sent from my LG-H811 using Tapatalk
Android_Guy said:
Hello everyone. I have rooted the G4, have SuperSU, and was going about installing TWRP. I used flashify and the TWRP version made for the H811 contained in these forums. Flashify seemed to install image correctly, but upon rebooting into recovery, I got a "Secure Boot Error 1003" and then a reboot to normal operation. I have searched and seen fixes for different devices, but none for the G4. Where did I go wrong and what can I do now?
Click to expand...
Click to collapse
You need to have OEM Unlock enabled in Developer Options, that how you can modify the boot files by unlocking the boot loader.
Sent from my LG-H811 using Tapatalk
paullueders223 said:
You need to have OEM Unlock enabled in Developer Options, that how you can modify the boot files by unlocking the boot loader.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thank you sir, that was the problem!
Hello,
Did you flash TWRP once again only ??
Because i have the same on a LG G4 H815 and i turned that on and flashed TWRP again using flashify but still the same problem.
Hope you can help me out of this
Re : I having same problem .
paullueders223 said:
You need to have OEM Unlock enabled in Developer Options, that how you can modify the boot files by unlocking the boot loader.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thanks my problem solve thanks you guys are great .
Secure boot error
billybong10 said:
Did you hit flash boot img in flashify instead of recovery img? You could try to boot into download mode and redo root process should fix then flash twrp using flash recovery img in flashify.
Sent from my LG-H811 using Tapatalk
---------- Post added at 05:29 PM ---------- Previous post was at 05:24 PM ----------
If redoing the root process doesn't fix you can try using the kdz file to return to stock, then re root and re flash twrp in flashify.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Could you give me a bit of help. I have the error code 3001. booting error. You mentioned using the KDZ file to return to stock. OK at this point Im lost. Would you be willing to show me slowly how to accomplish this.
It would be much appreciated
KK
succure boot error
hi i have the same problem but with my g3 d850 i rooted and installed twrp via flashify and apon reboot into recovery i get the same message sucure boot error error code 1003 and then twrp pops up and then i flash cm 12.1 and reboot same message again and then the phone is useable like i can txt and call and such but how can i fix it on my g3 because i dont think there is a OEM unlock in DEV options unless i missed it and if there is would i have to re root and re flash twrp and stuff plz help and also is tht normal like can i also if i wanted to like leave it there and not worry about it or should i fix that somehow please help thank you
Oem unlock didnt work on my (lg ls665. btw is this the same as LG LEON?)
Good day ppl.. so here'sy problem.. I downloaded a root app from Google play.. never pressed the developers thimg... And now my phone has the same secure boot 1003 message.. my phone is now on a boot loop at that screen.. I would love to try the KDZ thing.. bit I can't get in the phone
a1smkshp said:
Oem unlock didnt work on my (lg ls665. btw is this the same as LG LEON?)
Click to expand...
Click to collapse
Were you able to solve the problem of lg ls665?
Hey my lg g3 ls990 does the same .
wilsonjustin582 said:
hi i have the same problem but with my g3 d850 i rooted and installed twrp via flashify and apon reboot into recovery i get the same message sucure boot error error code 1003 and then twrp pops up and then i flash cm 12.1 and reboot same message again and then the phone is useable like i can txt and call and such but how can i fix it on my g3 because i dont think there is a OEM unlock in DEV options unless i missed it and if there is would i have to re root and re flash twrp and stuff plz help and also is tht normal like can i also if i wanted to like leave it there and not worry about it or should i fix that somehow please help thank you
Click to expand...
Click to collapse
Mine does the same . could you flash any roms without bricking?
wilsonjustin582 said:
hi i have the same problem but with my g3 d850 i rooted and installed twrp via flashify and apon reboot into recovery i get the same message sucure boot error error code 1003 and then twrp pops up and then i flash cm 12.1 and reboot same message again and then the phone is useable like i can txt and call and such but how can i fix it on my g3 because i dont think there is a OEM unlock in DEV options unless i missed it and if there is would i have to re root and re flash twrp and stuff plz help and also is tht normal like can i also if i wanted to like leave it there and not worry about it or should i fix that somehow please help thank you
Click to expand...
Click to collapse
same thing man i flashed the recovery pops the 1003 boot error then flashed ressurection remix with no problems but i wonder if going with it that way is okay or should i really fix the problem
paullueders223 said:
You need to have OEM Unlock enabled in Developer Options, that how you can modify the boot files by unlocking the boot loader.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
I get the same message on my lg transpyre. Tried to install twrp using flashify and now when I boot to recovery it stays in lg screen and says "secure booting error code 1003" if I hold down volume and power it will bypass and power up and works normal. Just can't do anything regarding recovery. Help me out. And in developer options I dontvhave an option to enable oem like you said to do.
lg g4c
I have a LG G4c. I rooted my phone.And I flash TWRP on my phone by TWRP Offical App and Flashify. I flashed and phone is off.After that my phone is restarted and I saw "secure booting error "error code : 1003" " on my phone's screen.I go to download mode .Connect my phone to my laptop.But I am not seeing my phone on my laptop. I go to Device Manager and yellow exclamation point appears.Help me pls.
THX FOR UR HELPS! :crying::crying::crying::crying::crying::crying:
I rooted today because I can't wait much longer for an OTA update. I'm trying to flash though ADB but can't because TWRP won't load ADB mode. I have reflashed TWRP recovery but it still doesn't work.
So can I do now? Can I use an OTG cable or download the image right to the device? Should I restore my backup and re-root without adding a custom recovery?
I'm so lost, any help would be great.
asarousi said:
I rooted today because I can't wait much longer for an OTA update. I'm trying to flash though ADB but can't because TWRP won't load ADB mode. I have reflashed TWRP recovery but it still doesn't work.
So can I do now? Can I use an OTG cable or download the image right to the device? Should I restore my backup and re-root without adding a custom recovery?
I'm so lost, any help would be great.
Click to expand...
Click to collapse
what are tou trying to accomplish?
you have twrp, use it to flash. you download what you need to the phone, then use twrp to flash it. adb doesnt flash anything.
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
i think i understand, youre trying to flash stovk marshmallow. you use fastboot to flash the factory image, while you are in your bootloader.
Hey @simms22 I just built aosp_shamu , just haven't flashed it myself
Sent from my Nexus 6 using Tapatalk
Yes, I'm trying to flash Marshmallow. I'm trying to access the file on my laptop to be sent to recovery through adb. How else can I get the file to my phone without adb. All the instructions involve adb, but I can't get it to go beyond "starting adb service" and it just sits there spinning its wheels. I tried originally to flash through Nexus Root Toolkit, but that failed do to it not seeing system.img.
asarousi said:
Yes, I'm trying to flash Marshmallow. I'm trying to access the file on my laptop to be sent to recovery through adb. How else can I get the file to my phone without adb. All the instructions involve adb, but I can't get it to go beyond "starting adb service" and it just sits there spinning its wheels. I tried originally to flash through Nexus Root Toolkit, but that failed do to it not seeing system.img.
Click to expand...
Click to collapse
USB-OTG. Or. adb push "file name" /storage/emulated/0/
Sent from my Nexus 6 using Tapatalk
---------- Post added at 20:36 ---------- Previous post was at 20:32 ----------
asarousi said:
Yes, I'm trying to flash Marshmallow. I'm trying to access the file on my laptop to be sent to recovery through adb. How else can I get the file to my phone without adb. All the instructions involve adb, but I can't get it to go beyond "starting adb service" and it just sits there spinning its wheels. I tried originally to flash through Nexus Root Toolkit, but that failed do to it not seeing system.img.
Click to expand...
Click to collapse
You want pure stock? I just made a shamu mm aosp straight from the source, its flashable. You'll have to flash mm gapps and su if you want root.
Official Team Bliss Flo, Deb, v400, v410, vk810, shamu-odexed Maintainer
Sent from my Nexus 6 using Tapatalk
blueyes said:
Hey @simms22 I just built aosp_shamu , just haven't flashed it myself
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
share, and ill probably flash with you. i miss the aosp browser
The Nexus Root Toolkit says I should force flash the image if system.img is not found, and it's not. Is this a good idea or will this brick my devic? Also, where can I find your build, blueeyes?
simms22 said:
share, and ill probably flash with you. i miss the aosp browser
Click to expand...
Click to collapse
http://downloads.blissroms.com/BlissPop/blueyes/
In that folder. Also made flo, deb, flounder
Sent from my Nexus 6 using Tapatalk
asarousi said:
The Nexus Root Toolkit says I should force flash the image if system.img is not found, and it's not. Is this a good idea or will this brick my devic? Also, where can I find your build, blueeyes?
Click to expand...
Click to collapse
get imgs here https://developers.google.com/android/nexus/images and follow this guide http://www.androidpolice.com/2014/11/12/running-into-the-dreaded-missing-system-img-error-flashing-android-5-0-factory-images-heres-how-to-get-around-it/
no tool kits just do it manually it easy its how i do all my updates
billycar11 said:
get imgs here https://developers.google.com/android/nexus/images and follow this guide http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
no tool kits just do it manually it easy its how i do all my updates
Click to expand...
Click to collapse
Link is just above your post. I agree. Toolkits are an emergency tool. Unless you fully understand what its doing, don't use it.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 20:58 ---------- Previous post was at 20:54 ----------
You want the factory image. Download it. Extract all zips. Install minimal adb and fastboot. Plug up to CPU , put device in bootloader mode. Simply start adb/fastboot, CD to where images are, type fastboot flash bootloader "name of BL", fastboot reboot bootloader, fastboot flash boot boot.img, system system.img, cache cache.img
Sent from my Nexus 6 using Tapatalk
simms22 said:
share, and ill probably flash with you. i miss the aosp browser
Click to expand...
Click to collapse
You try it Simms? Trying to build cm13 now, patched the forced encryption crap.. Had to operate on this branch but its finally building
Sent from my Nexus 6 using Tapatalk
blueyes said:
You try it Simms? Trying to build cm13 now, patched the forced encryption crap.. Had to operate on this branch but its finally building
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
nope. just saw it. im gonna download it, and flash tomorrow. now i need to find marshmallow gapps
simms22 said:
nope. just saw it. im gonna download it, and flash tomorrow. now i need to find marshmallow gapps
Click to expand...
Click to collapse
Ever used benzo gapps? http://renderserver.net/?dir=devs/xanaxdroid/benzo
Sent from my Nexus 6 using Tapatalk
blueyes said:
Ever used benzo gapps? http://renderserver.net/?dir=devs/xanaxdroid/benzo
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
:good:
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Rentom said:
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Click to expand...
Click to collapse
flash any custom kernel to get rid of that message
simms22 said:
flash any custom kernel to get rid of that message
Click to expand...
Click to collapse
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Rentom said:
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Click to expand...
Click to collapse
because google put it there, it is new.
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah I let twrp root it when it asked when I did it two months ago. Was that a bad thing? I thought I read that it was if you were rooting 6.0.1, but I was rooting 6.0 so I decided to see what would happen, and it went smoothly.
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I see. Makes sense. Alright, thanks. I already did flash it back to stock to update to 6.0.1, so I'm not sure why you told me to flash it back to stock and then install su 2.67.
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Mongo23ny said:
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Click to expand...
Click to collapse
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
simms22 said:
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
Click to expand...
Click to collapse
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Mongo23ny said:
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Click to expand...
Click to collapse
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Tried flashing twrp a couple of times, went back to stock recovery and then twrp. No luck. Also, phone will not boot with custom recovery only with stock. Not sure if I tried 3.0.0.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0?
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
no, do not keep system read only, ever.
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
Thanks for all your help, did a clean install, fastboot flashed 6.01. I had gotten that corrupt phone message when I rebooted again but I took some security update and that got rid of the message. I flashed twrp 3.0.0.0 and SuperSU 2.67 and got root back. No worries, thx again.
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
If you are using the systemless root method then yes, you do want to keep system read only.
alryder said:
If you are using the systemless root method then yes, you do want to keep system read only.
Click to expand...
Click to collapse
I kept it in read only, installed SuperSU 2.67 in twrp.