Related
Hey guys,
I wanted to flash the factory image KRT160 to my nexus 4 but accidentally flashed the one for the nexus 7.
I nerver had any problems flashing something to any phone I had but I guess just was too excited for KitKat
I can boot into fastboot and already tried to flash older factory images but nothing worked.
I also cannot boot into recovery. When I try it through fastboot or the toolkit it gives me an error (failed data transfer failure unknown error).
I really hope you can help me out because I wanted to debug an app ^^
Installing a kernel meant for another device is dangerous.
If flashing the factory images isnt working, i would suggest trying this.
Chromium_ said:
Installing a kernel meant for another device is dangerous.
If flashing the factory images isnt working, i would suggest trying this.
Click to expand...
Click to collapse
I know :/ The site automatically scrolled down to the 4.4 img and I didn't saw it at the top of the page and assumed it was the one for my N4.
But thanks for the fast reply, I will try it!
Thank you for being nice, not demanding things and not abusing caps. I've seen too many flashed the wrong image posts like that.
I think yours should serve as an example of how you should behave in such a situation... That is all.
Sent from my N4, wanna know what I am doing? Check http://team-fun.eu
SMillerNL said:
Thank you for being nice, not demanding things and not abusing caps. I've seen too many flashed the wrong image posts like that.
I think yours should serve as an example of how you should behave in such a situation... That is all.
Sent from my N4, wanna know what I am doing? Check http://team-fun.eu
Click to expand...
Click to collapse
Haha, i have to agree. The typical "flashed wrong kernel" post looks something like this:
:crying::crying::crying::crying: HALLPPPP PLZz... .fsdf FlASHeD wRong KerNal. Teh PhOne BrOke.....DeAd androidzz ReD triaNglez. PPlzzz hAlp mee. :crying::crying::crying::crying:
I'm not really new to all of this
But I wish I had looked twice ^^
I keep my fingers crossed for you to succeed. This should be a lesson to all of us to check twice before flashing. I had a hard bricked phone so I know what you feel.
Thanks for all your support! I managed to fight myself trough a whole bunch of (fastboot) commands and now I am able to boot 4.4!
the thread that @Chromium_ linked is your only hope. and i think that it will fix it, if you can get into download mode that is.
the flash-all bat file didn't work for me so I flashed each img individually with Wug's toolkit. I don't know what the best order for flashing all the separate images is, but it's prob not the way I did it.
What helped me was shutting down after flashing an image, vol-down+power booting into flashboot, repeat until each img was flashed. Then I wiped data/cache/dalvik while flashing SU, again with toolkit.
Hi guys, I recently had the misfortune of getting my Nexus 7 bricked.
Right. So if I claim warranty, how do I go about it? I don't mean the contacting htem and stuff. But what do I say to them to ensure maximum chance of getting the warranty?
I mean, I have voided the warranty by installing custom software on my Nexus. But is there any way I could actually logically persuade them to give me warranty? Or is it just luck? Hoping you get a not-so-smart technician to verify it is suitable for warranty?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Hi guys, I recently had the misfortune of getting my Nexus 7 bricked.
Right. So if I claim warranty, how do I go about it? I don't mean the contacting htem and stuff. But what do I say to them to ensure maximum chance of getting the warranty?
I mean, I have voided the warranty by installing custom software on my Nexus. But is there any way I could actually logically persuade them to give me warranty? Or is it just luck? Hoping you get a not-so-smart technician to verify it is suitable for warranty?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Just call & request an RMA number. If it's truly bricked, they will not be able to ascertain that you installed a custom ROM.
Thank you for that answer but I thought RMAs were for when you returned the device within the first 15days?
And sadly, its obvious that there is a custom rom instAlled. Its hardbricked with an unstoppable bootloop, showing Clockworkmod recovery
Sent from my GT-S5570 using xda app-developers app
What if i do specify some hardware fault that my nexus did have? Like the ghost touch issue. could i get it replaced under that pretext?
Sent from my GT-S5570 using xda app-developers app
Sorry for bumping but I really do need some help. Please?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Thank you for that answer but I thought RMAs were for when you returned the device within the first 15days?
And sadly, its obvious that there is a custom rom instAlled. Its hardbricked with an unstoppable bootloop, showing Clockworkmod recovery
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Why do you say that it is hard bricked? It's near impossible to hard brick a Nexus device. If you see the Google logo when the device powers on, you should be able to go into fastboot mode. Then just use fastboot commands to flash TWRP or CWM recovery and then just flash a ROM from recovery.
veeman said:
Why do you say that it is hard bricked? It's near impossible to hard brick a Nexus device. If you see the Google logo when the device powers on, you should be able to go into fastboot mode. Then just use fastboot commands to flash TWRP or CWM recovery and then just flash a ROM from recovery.
Click to expand...
Click to collapse
Yea, it is hard-bricked. As it is stuck in a bootloop involving CWM-Fastboot-CWM------
It's a long story, which is actually in this thread. http://forum.xda-developers.com/showthread.php?t=2468392
The circumstances of my bootloop are eerily similar, right down to the name of rom I flashed. Or it's probably because of that.
I flashed a new ROM (Kaos Droid 7.0.0) and the fitting gapps some minutes ago from CWM Touch. Everything worked as supposed, no errors, no warnings, nothing. Then I rebooted the Nexus 7 and now it's stuck in the worst bootloop I have seen so far:
The Google Screen appears, stays for some seconds, then I see a screen with the CWM Logo and the text "ClockworkmodRecovery 6.0.38", after this the device seems to reboot and the sequence starts from the beginning again.
I can not get into recovery, I can connect to my PC via USB but connection and disconnection happens every few seconds (because of the bootloop).
Click to expand...
Click to collapse
But I'd rather you answered my questions about warranty since this problem seems totally unfixable. It doesn't respond to any keypress I make except for long-press power.
nobody_nowhere said:
Yea, it is hard-bricked. As it is stuck in a bootloop involving CWM-Fastboot-CWM------
It's a long story, which is actually in this thread. http://forum.xda-developers.com/showthread.php?t=2468392
The circumstances of my bootloop are eerily similar, right down to the name of rom I flashed. Or it's probably because of that.
But I'd rather you answered my questions about warranty since this problem seems totally unfixable. It doesn't respond to any keypress I make except for long-press power.
Click to expand...
Click to collapse
Weird. But if it's rather obvious that you voided the warranty, I don't think they'll send you a new one.
That's the problem. The Google logo does appear and technically I'm supposed to be able to use my fastboot commands to undo the issue. But it doesn't work. Since the nexus doesn't respond to a single button press. So I cannot enter fastboot mode proper.
Yea, I knew that. But what if I get it replaced on some other reason than that?
Sent from my GT-S5570 using xda app-developers app
BrianXP7 said:
Did you somehow interrupted a bootloader flash or wrote "fastboot erase bootloader"? If not and the "Google" logo still appears, you really don't need an RMA.
Click to expand...
Click to collapse
No. It's like when you type reboot recovery. It just goes directly into cwm. And then it reboots and again. And again.
https://dl.dropboxusercontent.com/u/12668781/Nexus7_bootloop.mkv
BrianXP7 said:
Since you can't access MTP, you can try ADB Sideload. (It's a feature in later versions of ClockworkMod Recovery and Team Win Recovery. Why are you still using CWM by the way?) It'll transfer the flashable ZIP to the root of /sdcard and it'll flash immediately after.
RMAs should be only used for last resort bootloader bricks if you don't have access to the proprietary blobs. Luckily, you're fine.
Click to expand...
Click to collapse
Mate, my nexus does not respond in any way to the keypresses I make. So I cannot access clockworkmod, or fastboot mode, or even try to force a regular boot. It just bootloops on and on, completely unimpressed by my presses
BrianXP7 said:
Oh, my mistake. I didn't see your video. Sorry about that. (Bootlooping might be incorrect terminology for recovery. I'm not sure.) Try reflashing another recovery image like TWRP instead? That's the best I can give you for now.
Click to expand...
Click to collapse
Okay, I love that you're atleast trying to help. But the point is I literally have no way of flashing anything on it. I cannot do anything to it, bro. Whatever I do it just keeps bootlooping on and on. If I could access fastboot, I could easily fix this problem but I can't so.
I'd love your feedback concerning what I should do with regards to warranty
BrianXP7 said:
Again, it's not a bootloader brick. You don't need an RMA. In the video, you simply left it booting normally (then falling back to recovery). Also, it's not recovery's issue. It's probably the internal ROM that's made unbootable by some kind of OTA update.
To enter Fastboot mode, turn off your device completely. After, hold Power + Volume Down. Release Power (keep holding Volume Down) when "Google" displays. If done successfully, it'll display an Android lying down. That's Fastboot mode.
Unless you somehow damaged your hardware keys, you might be completely screwed. In order for your RMA to be accepted, you need to remove any trace of modification and relocking the bootloader. If you did restore it to an RMA acceptable state, it's already usable. (Screwing with the bootloader completely, or APX mode, will be accepted as they can't detect if you unlocked the bootloader or not.)
Click to expand...
Click to collapse
hmmmm. Is there a way of completely disabling the bootloader or something?
BrianXP7 said:
Yes, but you need access to Fastboot. If you did have access Fastboot, might as well fix it yourself. Basically, you flashed an incorrect bootloader image or interrupt the writing process. (Just don't think about it unless you have a bootloader backup.)
Click to expand...
Click to collapse
Okay, Can you do something for me?
Type su and then reboot recovery on the terminal.
Now when the Google Image is shown in the beginning, can you try to put it in Fastboot mode instead? Power + Volume Down, like you said.
Tell me if it works
BrianXP7 said:
What? I think you're over-complicating things. You don't even seem to try.
Just turn your device off. (Forced, normally, however you want.) Hold Power + Volume Down until "Google" appears. (That's when you release the power button but keep holding Volume Down.) If you see an Android laying down with a few options such as "Reboot normally", you're in Fastboot mode.
After that, just flash the stock factory images. It's as simple as that.
Click to expand...
Click to collapse
Did you try to do that for me?
I need You to do that for me. And tell me if it works. My Nexus 7 simply cannot be saved. Whatever I do, It doesn't respond. I know all about Fastboot mode, and recovery mode, and flashing factory images. I'm not a n00b like you seem to think. I do have a problem, but it seems to have been caused by random hardware fault rather than a fault on my part. But the result is the same.
nobody_nowhere said:
Did you try to do that for me?
I need You to do that for me. And tell me if it works. My Nexus 7 simply cannot be saved. Whatever I do, It doesn't respond. I know all about Fastboot mode, and recovery mode, and flashing factory images. I'm not a n00b like you seem to think. I do have a problem, but it seems to have been caused by random hardware fault rather than a fault on my part. But the result is the same.
Click to expand...
Click to collapse
@GedBlake;, you're the only person who understood my problem and tried to help me before. Could you perhaps do the same again?
nobody_nowhere said:
@GedBlake;, you're the only person who understood my problem and tried to help me before. Could you perhaps do the same again?
Click to expand...
Click to collapse
Hi, nobody_nowhere..
I will try, but I'm not quite what it is you're asking of me...
If it's concerning RMA, then I don't think I'm going to be of much help, I'm afraid... as I don't know the procedure for claiming under warranty (ie., RMA), having never done it myself.
My own Nexus 7 is just a liitle over a year old now, and I've so far been fortunate in having only had minor, and easily recoverable softbrick/bootloop type situations.
In your second post on this thread, you suggest that RMAs were time limited to just 15 days. I'm not completely sure, but I think this is incorrect. In most countries/jurisdictions, warranties usually run for 12 months. This is certainly the case here in the UK.
The thread you mention, well, having read it yourself, you'll know that I attempted to resolve the problem experienced by the OP of that thread... and it all came to nothing in the end.
There seems to be two recognisable categories of 'brick'... hardbrick, typically caused by a damaged, corrupt or wholly erased bootloader... and softbrick, which can have any number of causes, but is usually always resolvable - principally by accessing fastboot mode. Fastboot mode, is a sort of a 'get-out-of-jail' free card... and I've used it many times in the past.
But if you can't access fastboot mode (apropos of your current predicament), but the bootloader still works (if it didn't, NOTHING AT ALL would happen), your technically not hardbricked.
You have an unrecoverable soft brick... semi-hardbrick maybe? - a third category of 'brick'??
With regard to claiming under warranty... as I've already said, I really have no idea how to go about doing this, but I assume some sort of 'phone conversation would initially start the ball rolling and some questions would be asked of the owner of the Nexus 7...
...but, if it is unambiguously clear (and it sounds like it is, with CWM boot looping), that you've installed custom software, then there's no point in being disingenuous. As soon as they receive the device, they'll know. It you're honest with them, you might have a fair chance of them fixing it. If you lie outrightly, your credibility suffers.
Your best bet, I think, is to emphasize that's it's a hardware issue - emphasize the buttons aren't working properly. Emphasize that you're a knowledgeable Android user, and you're familiar with fastboot, and flashing custom software. The idea, here, is to make it more of a hardware problem, than a software problem - because it then throws the ball back into their court. And personally, I happen to think it is a hardware problem. I have no idea if this will work or not - I'm really just guessing here.
Whether installing custom software itself is sufficient to void warranty is a discussion that could fill an entire thread many pages over, such is the ambiguity of the issue.
It's generally considered, though, that unlocking the bootloader alone, is enough to leave your warranty in tatters... but flashing a Google factory stock image requires the bootloader to be unlocked anyway. So, I'm not quite sure how that contradiction squares itself away!
Indeed the flash-all.* script, that ships with factory stock images, unlocks the bootloader as matter of course. Of course, Google recommend re-locking the bootloader afterwards.
And what of Nexus 7 Jellybean 4.2.2 users, several months ago, who could root without unlocking the bootloader at all, using the motochopper "exploit".
Does rooting with an exploit count as installing custom software... you're messing with /system after all?
Ultimately though, I think that you may have to face an unpalatable truth - that tinkering with your device, does sometimes go wrong... in ways that leave even the most experienced users baffled (and I'm not even close to that level of knowledge and expertise).
There are some posters, here on XDA, who have in their sig., a list of previously owned devices... crossed out... and the word BRICKED next to them. These are the guys with thousands of posts to their name... and their 'graveyard' of dead devices are their metaphorical battlescars.
As soon as you type fastboot oem unlock, you're tacitly accepting that this may happen to you some day... you've effectively 'removed the back' of of that expensive clock/watch/HiFi system or Nexus 7... in the belief you can make it 'go' faster or perform better. Most of the time, you will be successful, and you will make it perform better, with whatever Custom ROM or kernel you've chosen to install.
But sometimes, something will go so horribly wrong... that there is no way back.
And all that is then left is the capriciousness of the company you have warranty with (via RMA)... and you're own negotiating skills.
I really do wish there was some button sequence, or command line I could suggest... but when dealing with the warranty people... you're on your own, sorry to say. Ultimately, and essentially... they may choose to repair it, or not. And beyond that, there's not much else I can add.
Except... best of luck.
Rgrds,
Ged.
Dear guys,
due to problems within this morning, i restarted my phone to wipe dalvik/cache.
But it occured that TWRP somehowe needs to have a password (which i didn't ever set though).
Didn't boot up at all now. Even with toolkit no chance to do anything with the device.
Any further suggestions/ideas?
Try flashing the factory image without using a tool kit. Google nexus 4 factory image. Download it to your pc and extract it. Run the flash-all.bat you'll find in there.
Sent from my Nexus 5
r4ff0r said:
Dear guys,
due to problems within this morning, i restarted my phone to wipe dalvik/cache.
But it occured that TWRP somehowe needs to have a password (which i didn't ever set though).
Didn't boot up at all now. Even with toolkit no chance to do anything with the device.
Any further suggestions/ideas?
Click to expand...
Click to collapse
Some Partitions of the phone have got some bad blocks causing it to act in such a way !! Seems RMA(if available) is the best recourse since there is no definative solution to this problem !! You can try hard reboot as well as someone once pointed out that his n4 magically restored during it but others dint have that much of luck !! Also u could give LGNPST a try but since that also writes the partition it is highly unlikely to get you through !! One Solution I know will surely work is Qualcomm PST using the HighSpeed USB Device . But unfortunately we need an expert help, probably a Qualcomm employee to get in touch with since the tool has still not been cracked by anyone for n4 though I read somewhere that someone was able to restore using QPST !! Also mostly a JTAG Repair can help you but thats a rip off !! I'll anyday prefer a official LG/Google Repair over a JTAG !!
Hope you find my post useful !!
THanks Guys,
JD5, it didn't work.
Corresponding to Nabendu's post i guess it is the issue mentioned here.
http://forum.xda-developers.com/nexus-4/help/dead-nexus-4-strange-advice-welcome-t2259334
So therefore i don't see any chance :-/
r4ff0r said:
THanks Guys,
JD5, it didn't work.
Corresponding to Nabendu's post i guess it is the issue mentioned here.
http://forum.xda-developers.com/nexus-4/help/dead-nexus-4-strange-advice-welcome-t2259334
So therefore i don't see any chance :-/
Click to expand...
Click to collapse
I was afraid of that. Try one thing. Relock the bootloader, fastboot oem lock, then re-boot and see if the bootloader locks. If it doesn't, and it probably won't, then rma is your option.
Edit, haha, I just read that thread you posted and they tried the same thing
Sent from my Nexus 5
i was already trying that. at first it seems that the bootloader got locked again but right after restart it is already unlocked again.
I guess RMA will cause problems due to the fact that it was a rooted Nexus, using a custom rom.
r4ff0r said:
i was already trying that. at first it seems that the bootloader got locked again but right after restart it is already unlocked again.
I guess RMA will cause problems due to the fact that it was a rooted Nexus, using a custom rom.
Click to expand...
Click to collapse
Google seems to have been pretty good with rma's when it's a hardware failure. Pretty sure your emmc is borked. But you never know until you send it in. Hopefully there won't be a problem.
Sent from my Nexus 5
Ok I'll give it a try on monday. But as far as i know, i'll need to call them first.
I could imagine that they'll try to let me wipe my data or give me any kind of instructions to see if they can resolve the problem right away? What do i tell them?
At latest when they'll lead me to the recovery i'll get stuck using TWRP at latest.
Any kind of conversation dialogue i can follow up?
Let's try one more thing, inside the factory image is a zip file, extract that. In there is recovery.img. Put that file in the same folder as fastboot.exe. In fastboot try fastboot flash recovery recovery.img
If it works it'll put the stock recovery on.
Sent from my Nexus 5
Nope, same issue " flash write failure"
I can't get any kind o access...
But don't leave any more thoughts on it. Won't work though, i won't want to bother you all the time
jd1639 said:
Let's try one more thing, inside the factory image is a zip file, extract that. In there is recovery.img. Put that file in the same folder as fastboot.exe. In fastboot try fastboot flash recovery recovery.img
If it works it'll put the stock recovery on.
Sent from my Nexus 5
Click to expand...
Click to collapse
It won't let you flash that either to the best of my knowledge !! Just don't tell those operators that you have unlocked your bootloader and have a custom recovery !! Basically they won't tell u to go into stock recovery !! They'll just ask you hard reset the phone using physical keys !! Bdw check my pm !!
r4ff0r said:
Nope, same issue " flash write failure"
I can't get any kind o access...
But don't leave any more thoughts on it. Won't work though, i won't want to bother you all the time
Click to expand...
Click to collapse
Np, not sure what to tell them. It still boots I assume so you can't tell them it won't boot. I guess just the truth, it is a developer phone after all so it should be flashable
Sent from my Nexus 5
Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks
ShaunWinSC said:
Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks
Click to expand...
Click to collapse
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.
just4747 said:
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.
Click to expand...
Click to collapse
It really doesn't matter. I just would like a cleaner boot cycle. Plus I know the MXPE is able to remove this warning.
There is no way around it right now. I had a kernel on my N6 that didn't show the message so it could come sooner or later, but it doesn't hurt anything. It's only a warn. There are three stages, I think; yellow, orange and red.
fury683 said:
There is no way around it right now. I had a kernel on my N6 that didn't show the message so it could come sooner or later, but it doesn't hurt anything. It's only a warn. There are three stages, I think; yellow, orange and red.
Click to expand...
Click to collapse
what do you mean? My warning is in orange.
collinjm01 said:
what do you mean? My warning is in orange.
Click to expand...
Click to collapse
http://www.androidauthority.com/verified-boot-warnings-in-android-6-0-marshmallow-650368/
ShaunWinSC said:
Is there a way to remove the warning on boot, after the bootloader has been unlocked. Thanks
Click to expand...
Click to collapse
.
After reading info on Android Security in this link you should know more about Verified Boot.
.
http://source.android.com/devices/tech/security/verifiedboot/verified-boot.html
.
.
Techie info about SafetyNet anti-tamper detection here.
https://koz.io/inside-safetynet/
.
Interesting reading about what info Google is now able to pull from youe device.
It's an eyesore no doubt about it but I hardly reboot so it's somewhat bearable.
^^^ why did you bump a thread that died November 11 :lol:
Someone found a way to get rid of this message a while back on the 5X. It worked perfectly for me on that phone. I imagine the method would be the same on the 6P. If someone wants to give the img files a shot from the below link and report back, it might be exactly what we are looking for.
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
The command to flash the file is:
fastboot flash imgdata imgdata.img (replace "imgdata.img" with the actual name of the img file)
I'd test it myself but I JUST setup my brand new 6P and don't feel like spending the evening troubleshooting if something goes wrong.
sn0warmy said:
Someone found a way to get rid of this message a while back on the 5X. It worked perfectly for me on that phone. I imagine the method would be the same on the 6P. If someone wants to give the img files a shot from the below link and report back, it might be exactly what we are looking for.
http://forum.xda-developers.com/showpost.php?p=63826602&postcount=7
The command to flash the file is:
fastboot flash imgdata imgdata.img (replace "imgdata.img" with the actual name of the img file)
I'd test it myself but I JUST setup my brand new 6P and don't feel like spending the evening troubleshooting if something goes wrong.
Click to expand...
Click to collapse
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Edit 1: A modified system image did not make a difference as it displayed the same error message. I'm going to back up the rest of my stuff I need off the phone and try to flash one of the zips instead in TWRP.
Edit 2: Looks like flashing in TWRP was a no-go as well. I don't have the unlocked bootloader warning anymore, but the red corrupted device warning is still there. I guess it's not possible for now.
j.bruha said:
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Click to expand...
Click to collapse
Thanks for this update! Will look forward to seeing you post back...while it's not life or death to me it is a rather silly and pointless message by the 100th time I've seen it lol so I would disable it in a heartbeat if I could
just4747 said:
No, but why does it matter? It will go away if/when you re-lock it for whatever reason.
Click to expand...
Click to collapse
No? How about Ya there should be maybe the cause they have a remove mod for the 5x over in the 5x XDA side.
Maybe the same process cause I wondered this question myself
Sent from my Nexus 6P using XDA Free mobile app
j.bruha said:
I happen to be in the middle of a replacement process for my 6P and still have the old and new devices. I just finished using one of those img files to get rid of my fiance's boot warning on her 5X and decided to try it out on the 6P I'm sending back to Google. Unfortunately, it looks like it wouldn't flash at all. After attempting to write the file, I get an error that reads "FAILED (remote: permission denied!)". I also only have the bootloader unlocked and no other modifications, so I'm going to mess some stuff up and report back.
Edit 1: A modified system image did not make a difference as it displayed the same error message. I'm going to back up the rest of my stuff I need off the phone and try to flash one of the zips instead in TWRP.
Edit 2: Looks like flashing in TWRP was a no-go as well. I don't have the unlocked bootloader warning anymore, but the red corrupted device warning is still there. I guess it's not possible for now.
Click to expand...
Click to collapse
The /imgdata partition is commented out in fstab in the boot.img. If I modify the boot.img, would you be willing to flash the boot.img and then try one of the /imgdata modification files once more?
In case you are willing, here is the boot image with /imgdata uncommented: http://www.mediafire.com/download/cwpfkjgqyw9bwcx/Stock_NoEncrypt_uncomment-imgdata_Kernel_6.0.1.zip
MD5Sum: 94f9bc6b01f7294b8835d9f28b7c6ed3
You can flash it in TWRP, or extract the boot.img from the zip and flash it with fastboot in bootloader mode.
You need a custom bootloader to remove this. No kernel will take care of it for you. The warning message is within the bootloader.img. The 5x and the 6p are completely different phones. Regardless of the fact that they are both Nexus devices. What works for one will not necessarily work for the other.
Sent from my XT1080 using Tapatalk
Yeah, I've been quickly discovering that over the past 2 days. Very different phones indeed.
bouchigo said:
The /imgdata partition is commented out in fstab in the boot.img. If I modify the boot.img, would you be willing to flash the boot.img and then try one of the /imgdata modification files once more?
In case you are willing, here is the boot image with /imgdata uncommented: http://www.mediafire.com/download/cwpfkjgqyw9bwcx/Stock_NoEncrypt_uncomment-imgdata_Kernel_6.0.1.zip
MD5Sum: 94f9bc6b01f7294b8835d9f28b7c6ed3
You can flash it in TWRP, or extract the boot.img from the zip and flash it with fastboot in bootloader mode.
Click to expand...
Click to collapse
Just a side note for all who will wonder or ask for the hell of it I tried
Nexus 5x mod file to remove this on a 6p and it doesnt ..was worth a shot.But it did when I had the 5x
Sent from my Nexus 6P using XDA Free mobile app
androidddaaron said:
Just a side note for all who will wonder or ask for the hell of it I tried
Nexus 5x mod file to remove this on a 6p and it doesnt ..was worth a shot.But it did when I had the 5x
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I tried it earlier in the morning, and no go. I believe the /imgdata partition does not exist in the N6P, that's most likely why it was commented out from fstab.
Sent from my Nexus 6P using Tapatalk
SyCreed said:
hey guys i don't want to open a new topic cuz i think it's related here -
If i go back to fully stock, and re-lock the bootloader + factory reset after those operation, no one actually can know if the device was rooted or unlocked right?
Click to expand...
Click to collapse
Correct, if you do that it will be like out of the box.
I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.
convolution said:
I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.
Click to expand...
Click to collapse
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk
dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...
convolution said:
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...
Click to expand...
Click to collapse
It has been awhile since I rooted any phone, but yes, pressing power to continue was what I remember. And, yes annoying, but not fatal !
Sent from my PH-1 using Tapatalk
It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.
GryphKid44 said:
It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.
Click to expand...
Click to collapse
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?
I would think that would do the trick. In my case I knew the system was issue so I just flashed system. I find fastboot extra finicky on this phone. Did you happen to notice if something errored in the script?
convolution said:
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?
Click to expand...
Click to collapse
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck
wolfu11 said:
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck
Click to expand...
Click to collapse
I do... but my wifi doesn't work as well, so I think I did something wrong.
convolution said:
I do... but my wifi doesn't work as well, so I think I did something wrong.
Click to expand...
Click to collapse
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.
wolfu11 said:
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.
Click to expand...
Click to collapse
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?
convolution said:
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?
Click to expand...
Click to collapse
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.
wolfu11 said:
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.
Click to expand...
Click to collapse
no need for twrp?
you follow this one?
convolution said:
no need for twrp?
you follow this one?
Click to expand...
Click to collapse
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.
wolfu11 said:
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.
Click to expand...
Click to collapse
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...
convolution said:
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...
Click to expand...
Click to collapse
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.
spotmark said:
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.
Click to expand...
Click to collapse
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.
delete
If it works, you should worry about that message at all.
convolution said:
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.
Click to expand...
Click to collapse
The slot thing is pretty new in general. This doc has some explanation for the architecture of our phones: http://mata.readthedocs.io/en/latest/
Once you get the hang of it, it's pretty simple to deal with.
BTW, awesome signature. PTL, SDG. :victory: