Database Users

Flash Memory Broken

Hey there I am really upset. ^^
Yesterday - before going to sleep - my nexus 7 died. The battery was drained, so it turned off. I plugged it in quickly, tried to turn it back on. It booted up, but rebooted directly after the lockscreen was visible. It did so several times until it started to give me artifacts for some seconds after it turned itself off before rebooting. I decided to leave it till the next morning b/c my gf was already quite angry. So the next morning i picked it up, turned off at that time. Turned it on and couldn't get past the bootloader. Recovery doesn't work either. Trying to flash the stock system image through fastboot gives the following:
Code:
erasing 'system'...
OKAY [ 2,532s]
sending 'system' (471804 KB)...
OKAY [ 56.022s]
writing 'system'...
FAILED (remote: (FileWriteFailed))
finished. total time: 58,598s
flashing TWRP 2.5.0.0 looks very similar but doesnt take as long fastboot-booting TWRP works though. And if i try to use the built in File Manager everything including the sdcard-folder is empty. ADB is inaccessible from recovery.
Any1 having or had a similar problem? I already contacted ASUS RMA, but i want to try something else until I get a reply and my baby gets taken away
Just in case some1 reads this: sent it to ASUS for RMA. They apparently got it, the status is
Product repair is in progress.-[WF4] Wait for Customer Confirmation-Customer Induced Damage \Out-Of-Warranty
Click to expand...
Click to collapse
now. Hope they dont try to do with me what they did with several transformer users. BTW: How should i be able to break the flash memory when running full stock with root? Seems like fastboot oem lock would've been a good idea prior to sending it in..
Update2: They sent me back a picture of a Nexus 7 booting up TWRP. I never even installed TWRP on my Nex7. They also apparently lost the copy of the original bill I put in the packet, so I had to send them another scan of it.
I sent them an e-mail explaining how illogical it is that my tablet had TWRP on it and how I expected them to repair it after losing the copy of my bill and accusing me of lying to them..

Stock rom recovery failed need a lil help

Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Is there a way to force a flash to ignore all signatures and i will go back to an earlier rom from google that worked properly?
or do i need a new tablet as Asus support has been less than useful?
Cheers

Support
ScoTTisH-GingeR said:
Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Is there a way to force a flash to ignore all signatures and i will go back to an earlier rom from google that worked properly?
or do i need a new tablet as Asus support has been less than useful?
Cheers
Click to expand...
Click to collapse
Hello,
Hvae you tried flashing a recovery though fastboot? Once you have done this you should be able to sideload a new rom and BAM your done.
See here for fastboot flashing a new recovery: http://teamw.in/project/twrp2/103
See here for sideloading in recovery: http://teamw.in/ADBSideload

[email protected] said:
Hello,
Hvae you tried flashing a recovery though fastboot? Once you have done this you should be able to sideload a new rom and BAM your done.
See here for fastboot flashing a new recovery
See here for sideloading in recovery:
Hey Scott cheers for the reply here is the result of the attempting to flash twrp.
C:\nexus\4.4.4>fastboot flash recovery openrecovery-twrp-2.7.1.1-grouper.img
sending 'recovery' (8502 KB)...
OKAY [ 1.039s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 3.863s
Any more ideas or am i binning my nexus?
Click to expand...
Click to collapse

ScoTTisH-GingeR said:
Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Hello,
My August 2012 Nexus 7 got same issue.
Boot loop up to animated circles or Android update.
Rooted. CWM recovery. Stock ROM 4.4.3
General remark/ the device was getting really slow in spite of regular use of Lagfix.
Fastboot OK. That is in fact the only way to power off the device.
Wipe Data / Factory reset had no effect on bootloop.
Errors trying to flash official Factory image through adb: example " recovery.sig files not found". I tried to flash them individually
I tried the Nexus Toolkit: Error trying to load a factory image. Error trying to return to stock recovery.
I suspect a memory issue.
Finally I just return this morning the device to ASUS France, after requesting a Return Agreement.
No more warranty; I wonder if the resulting cost are worst this action if tablet is not reparable.
I am really upset.
Click to expand...
Click to collapse

Hello,
Have you tried the steps to flash a system imagem, all you need is to have access to fastboot. Please visit: https://developers.google.com/android/nexus/images for instructions on how to do this.
I hope these steps help, If you need further assistance you can email me at [email protected]. Be sure to place case number N140811561 in the subject line for reference.
Regards,
Scott
ASUS Customer Loyalty

Motherboard issue
[email protected] said:
Hello,
Have you tried the steps to flash a system imagem, all you need is to have access to fastboot. Please visit: https://developers.google.com/android/nexus/images for instructions on how to do this.
I hope these steps help, If you need further assistance you can email me at [email protected]. Be sure to place case number N140811561 in the subject line for reference.
Regards,
Scott
ASUS Customer Loyalty
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------------------------
I just got the answer from Ename, ASUS repair contractor in France.
Motherboard got problems. Need replacement.
Total cost 192 €.
Basically I have better to buy a new one.
That is really bitter after just 2 years .....!!!!!
Is the 2013 model more robust?

marcelin99 said:
-----------------------------------------------------------------------------------------------------------
I just got the answer from Ename, ASUS repair contractor in France.
Motherboard got problems. Need replacement.
Total cost 192 €.
Basically I have better to buy a new one.
That is really bitter after just 2 years .....!!!!!
Is the 2013 model more robust?
Click to expand...
Click to collapse
Hello,
The Nexus 7 21013 is slightly lighter, has a better resolution (1920 x 1200 pixels), adds a rear camera and sports the Qualcomm Snapdragon S4 Pro APQ8064 with 2048 MB RAM. So it is a nice increase in the specs. With a your repair cost of 192 it might be better to consider upgrading your Nexus experience. If you need further support feel free to email me at [email protected] with case number in the N140820223 subject line.
Regards,
Scott
ASUS Customer Loyalty

[Q] Development for the M.O.J.O

Currently the M.O.J.O has been a very unsuccessful device and there hasn't been any recent development. I would like to give a try at a few things such as a custom recovery
I am asking for someone to provide with me with the output of the following commands
Start adb shell
Code:
cat proc/iomem > iomem.txt
Code:
cat proc/partitions > partitions.txt
Code:
getprop > prop.txt
I've attached a test cwm recovery.img DO NOT FASTBOOT FLASH RECOVERY!!! use the below command to test the image
Code:
fastboot boot recovery.img

Hi,
Thanks heaps for helping dev on the mojo!
I'm keen to help!
Done.. I"ll try the image now.
./fastboot-linux -i 0x0738 devices
15C40C1C30400000012FC8380 fastboot
./fastboot-linux -i 0x0738 boot recovery.img
downloading 'boot.img'...
OKAY [ 0.375s]
booting...
OKAY [ 0.001s]
finished. total time: 0.377s
Click to expand...
Click to collapse
It does nothing for about a minute, then the blue light comes on the screen says 'mode not supported', tried on a monitor (with a HDMI to DVI) same 'mode not supported' then no signal.
Not sure how you would get debugging info out ... that's been the main problem
Anyway, if you need any more info or test, just ask.

gwaldo said:
Hi,
Done.. I"ll try the image now.
Click to expand...
Click to collapse
Thanks it helps a lot with the device tree. How did the recovery turn out?

Unjustified Dev said:
Thanks it helps a lot with the device tree. How did the recovery turn out?
Click to expand...
Click to collapse
Didn't do anthing, or at least I couldn't see it on my TV nor monitor :/

gwaldo said:
Didn't do anthing, or at least I couldn't see it on my TV nor monitor :/
Click to expand...
Click to collapse
Thanks it could be a kernel issue I'm working on kexec hardboot I'm going to remove that for now and build again.
edit: Attached new image as well as a new adb and fastboot binary for you with adb and fastboot id added
https://github.com/TeamRegular/android_system_core/commit/effaa8a925b68651dbb1a0d50cffb81e57df9f5d
I replaced mine in /usr/bin/ with these and they still work as normal for me.

Unjustified Dev said:
Thanks it could be a kernel issue I'm working on kexec hardboot I'm going to remove that for now and build again.
edit: Attached new image as well as a new adb and fastboot binary for you with adb and fastboot id added
https://github.com/TeamRegular/android_system_core/commit/effaa8a925b68651dbb1a0d50cffb81e57df9f5d
I replaced mine in /usr/bin/ with these and they still work as normal for me.
Click to expand...
Click to collapse
Wow, I didn't even know fastboot had a github, you're very pro sir! :good:
I run it now:fingers-crossed:
using your exe (on my 32bit Mint linux 17):
./fastboot -i 0x0738 boot recovery-v2.img
downloading 'boot.img'...
OKAY [ 0.376s]
booting...
OKAY [ 0.001s]
finished. total time: 0.378s
Click to expand...
Click to collapse
But again same result

gwaldo said:
Wow, I didn't even know fastboot had a github, you're very pro sir! :good:
I run it now:fingers-crossed:
Click to expand...
Click to collapse
You can build those in an android environment that's actually from the source you would use to build a full rom I just forked the tree from CyanogenMod added the id and compiled it.

Unjustified Dev said:
You can build those in an android environment that's actually from the source you would use to build a full rom I just forked the tree from CyanogenMod added the id and compiled it.
Click to expand...
Click to collapse
Not sure what else to do, to get into the existing mojo's recovery, is pretty hit and miss for me (I get unsupported display a lot until it work) so not sure if that's normal... i'm a android dev noob, so don't really know how to use adb to debug the boot image.
Not sure if having a usb keyboard/mouse plugged in will help?
Edit:
Also the nvidia shield (Tegra4) is similarly spec'ed but not sure about the HW components.
It is a well documented and hacked device.
I'm sure so of what they do is applicable to mojo also?

gwaldo said:
Not sure what else to do, to get into the existing mojo's recovery, is pretty hit and miss for me (I get unsupported display a lot until it work) so not sure if that's normal... i'm a android dev noob, so don't really know how to use adb to debug the boot image.
Not sure if having a usb keyboard/mouse plugged in will help?
Click to expand...
Click to collapse
You should be able to run adb reboot recovery while the device is booted.
edit to your edit: The shield work is not applicable to the mojo but I have worked with the shield as well as ported cwm easily I'm wondering why this img won't boot I've seen the troubles in the other thread. I'm thinking maybe install the image to your recovery partition and adb reboot recovery it will not brick the device as the recovery image is safe on a partition that doesn't effect the booting process the boot partition on the other hand I would never fastboot flash it without testing if it boots first. I'm wondering if the img is too big for the partition maybe. I'm not sure the partition is 8mb the image is 7.6 I'm going to change the compression and see if it boots. You also no longer need the -i 0x0738 when using fastboot
Last edit could you pull proc/config.gz

Unjustified Dev said:
You should be able to run adb reboot recovery while the device is booted.
edit to your edit: The shield work is not applicable to the mojo but I have worked with the shield as well as ported cwm easily I'm wondering why this img won't boot I've seen the troubles in the other thread. I'm thinking maybe install the image to your recovery partition and adb reboot recovery it will not brick the device as the recovery image is safe on a partition that doesn't effect the booting process the boot partition on the other hand I would never fastboot flash it without testing if it boots first. I'm wondering if the img is too big for the partition maybe. I'm not sure the partition is 8mb the image is 7.6 I'm going to change the compression and see if it boots. You also no longer need the -i 0x0738 when using fastboot
Last edit could you pull proc/config.gz
Click to expand...
Click to collapse
I think it is booting, I just can't get a working display.
With a keyboard I can boot your recovery image and do a ALT Printscreen O and it turns off as expected.
I know a few of these keys from here: http://forum.xda-developers.com/showpost.php?p=54517256&postcount=32
I'll get that file for you now, I don't have adb set up.

gwaldo said:
I think it is booting, I just can't get a working display.
With a keyboard I can boot your recovery image and do a ALT Printscreen O and it turns off as expected.
I know a few of these keys from here: http://forum.xda-developers.com/showpost.php?p=54517256&postcount=32
I'll get that file for you now, I don't have adb set up.
Click to expand...
Click to collapse
Thanks I compared the defconfig to the one in the stock source and it was different compiling again.

Unjustified Dev said:
Thanks I compared the defconfig to the one in the stock source and it was different compiling again.
Click to expand...
Click to collapse
I'm running this update mojo-signed-ota-MO0202-WW.zip
from ftp://86.54.116.234/pub/software/mojo/firmware/
I think the kernel src version is from the first firmware update (mojo-signed-ota-MO0110-WW.zip) or it could be even before that.
I think the problem (maybe just mine) is I can't get a display in recovery with out a lot of F'ing around.. ie: randomly pressing home up/down ALT PRNTSCRN I etc... but like I said, your image does work as it responds to ALT PRNTSCN O
---------- Post added at 01:49 PM ---------- Previous post was at 01:33 PM ----------
Unjustified Dev said:
Thanks I compared the defconfig to the one in the stock source and it was different compiling again.
Click to expand...
Click to collapse
SH!T IT WORKS!!!
I couldn't get a display, so I ran it through my HDMI capture device, not expecting to record anything any it worked!!!
I'm uploading a vid now!
Congrats dude! you did it!

gwaldo said:
I'm running this update mojo-signed-ota-MO0202-WW.zip
from ftp://86.54.116.234/pub/software/mojo/firmware/
I think the kernel src version is from the first firmware update (mojo-signed-ota-MO0110-WW.zip) or it could be even before that.
I think the problem (maybe just mine) is I can't get a display in recovery with out a lot of F'ing around.. ie: randomly pressing home up/down ALT PRNTSCRN I etc... but like I said, your image does work as it responds to ALT PRNTSCN O
Click to expand...
Click to collapse
Here's the change https://github.com/TeamRegular/andr...mmit/e82e271131d30290022f301b70089cf2fb9224d3
It's also enabled on the shield I can't remember but it looks like I did it when I worked on the shield as well since it's not enabled in the defconfig they give us it's probably enabled in their nvidia source builds I can't remember how all that works it's been a while since I had shield source downloaded but hopefully this is the problem.

Unjustified Dev said:
Here's the change https://github.com/TeamRegular/andr...mmit/e82e271131d30290022f301b70089cf2fb9224d3
It's also enabled on the shield I can't remember but it looks like I did it when I worked on the shield as well since it's not enabled in the defconfig they give us it's probably enabled in their nvidia source builds I can't remember how all that works it's been a while since I had shield source downloaded but hopefully this is the problem.
Click to expand...
Click to collapse
I'll test it out, but your previous image works, my TV nor monitor likes the resolution (guessing).
Any chance of defaulting to a low res? or booting into a safe mode?

gwaldo said:
I'll test it out, but your previous image works, my TV nor monitor likes the resolution (guessing).
Any chance of defaulting to a low res? or booting into a safe mode?
Click to expand...
Click to collapse
I guess I would have to switch to twrp recovery I'm not sure what theme would fit but I added the size for mojo already It's just a matter of building it. Honestly most of the time twrp display code works better than cwm.
https://github.com/TeamRegular/android_bootable_recovery/commits/android-4.4

Here's the video, just hitting home and up/down keys.
https://www.youtube.com/watch?v=5A4yDR2Z_GU
Unjustified Dev said:
I guess I would have to switch to twrp recovery I'm not sure what theme would fit but I added the size for mojo already It's just a matter of building it. Honestly most of the time twrp display code works better than cwm.
https://github.com/TeamRegular/android_bootable_recovery/commits/android-4.4
Click to expand...
Click to collapse
It could be my TV/monitor is just old... but it's strange I don't have a problem with the MOJO/laptop etc.
If you build twrp, I'm happy to test it out also.

gwaldo said:
Here's the video, just hitting home and up/down keys.
https://www.youtube.com/watch?v=5A4yDR2Z_GU
It could be my TV/monitor is just old... but it's strange I don't have a problem with the MOJO/laptop etc.
If you build twrp, I'm happy to test it out also.
Click to expand...
Click to collapse
So this is the first booting just not outputting to screen very strange I'll look into it. I'll compile twrp now it will take over an hour to build I have to setup device to compile in omni rom environment. I'll pm you the build.

Unjustified Dev said:
So this is the first booting just outputting to screen very strange I'll look into it. I'll compile twrp now it will take over an hour to build I have to setup device to compile in omni rom environment. I'll pm you the build.
Click to expand...
Click to collapse
cwm-recovery.img also boots.
Really strange that I can't see a display but I can record the HDMI output on my AverMedia Capture HD II C285 as it's really sensitive to HDMI.
Maybe a frequency/refresh rate setting?
With the MOJO's recovery menu on my monitor I get:
MODE NOT SUPPORTED
H: 67.5KHZ
V: 60.0HZ
With your firmware:
MODE NOT SUPPORTED
H: 67.2KHZ
V: 59.7HZ
My TV is PAL, if that helps.
I'm guessing because the MOJO has no screen it's not sending a 100% correct HDMI stream.
Whatever the issue is, it's also in the default recovery.
Anyway, I'm sure others will try out your recovery image and we'll get feed back.
No problem, happy to test it out

gwaldo said:
cwm-recovery.img also boots.
Really strange that I can't see a display but I can record the HDMI output on my AverMedia Capture HD II C285 as it's really sensitive to HDMI.
Maybe a frequency/refresh rate setting?
With the MOJO's recovery menu on my monitor I get:
MODE NOT SUPPORTED
H: 67.5KHZ
V: 60.0HZ
With your firmware:
MODE NOT SUPPORTED
H: 67.2KHZ
V: 59.7HZ
My TV is PAL, if that helps.
I'm guessing because the MOJO has no screen it's not sending a 100% correct HDMI stream.
Whatever the issue is, it's also in the default recovery.
Anyway, I'm sure others will try out your recovery image and we'll get feed back.
No problem, happy to test it out
Click to expand...
Click to collapse
I'll take a look into some later commits from nvidia git the mojo kernel is quite outdated. I found last merged commit on this page
I tried to pick each one and ended up with a ton of issues I will try again in the next few days doing page by page only and building
https://github.com/somcom3x/android_kernel_nvidia_tegratab/commits/cm-11.0?page=24

gwaldo said:
Here's the video, just hitting home and up/down keys.
https://www.youtube.com/watch?v=5A4yDR2Z_GU
It could be my TV/monitor is just old... but it's strange I don't have a problem with the MOJO/laptop etc.
If you build twrp, I'm happy to test it out also.
Click to expand...
Click to collapse
Interesting, im using a monitor which supports many formats and it wasnt able to pick up when i tried my hand at CWM, alas i didnt have a screen capture device so i just assumed it was something wrong with foxconn's programming/setup than just graphics not displaying properly.

Near brick xt1575 no BT or WiFi

I could really use some help. I'm at the edge of my patience and have tried pretty much everything I can think of. I say near brick cause a phone without WiFi and BT is kinda useless.
Here's the back story. I had my previous xt1575 stolen. I purchased a used one off ebay. I received it, only to find it was bootloader unlocked, rooted. Not an issue in theory but I wasn't told that. Ok, upon trying the phone it worked but the battery would last 3 hours, it would have random reboots and would run so hot i could hardly hold the phone. I figured it was a faulty kernel. I flashed a new kernel and stock rom. Battery life went back to almost perfect but was off by about 20%. The random reboots were still an issue, but everything else seemed to work. A randomly rebooting phone is far from ideal. I figured I'd keep trying. Maybe it was a software issue. I would get random results with different roms. And the rebooting really seemed to occur when I had all my apps downloaded. So, I decided to run to flash again and run lean and see if with just the default apps whether it would reboot. After the flash, I waited a few hours, then BT and WiFi just stopped working. No go. The actual toggles revert to off position essentially immediately and neither turn on. I've since tried FDRs, different roms, different kernels, no luck. No idea what to do at this point. It could be hardware, obviously. It could be that the wifi chip was faulty and causing the overheating/battery drain from before, and finally after running so hot that one day before I flashed, it just did final damage to the chip that came to pass 3 days later. I don't know. It's possible but i somehow feel like it's a SW issue. I could send it back but it's complicated and i would really prefer to see if I can get this resolved. I've reflashed the modem bin files of stock roms, etc. Another issue i get often is when i try flashing, I get the writing 'boot'... (bootloader) Preflash validation failed FAILED (remote failure) and other such failures. Additionally, TWRP often just disappears. Aside from that, the OS, usually runs fine. I can't download apps obviously due to no WiFi, but everything else seems fine and I haven't had any reboots since the wifi/bt stopped working. I don't know if it's a partition issue, or hardware or what. I could use some advice. I'm at the limit of my patience and my knowledge here.
Let me know what you guys need and thanks ahead of time for your help.

vijn said:
I could really use some help. I'm at the edge of my patience and have tried pretty much everything I can think of. I say near brick cause a phone without WiFi and BT is kinda useless.
Here's the back story. I had my previous xt1575 stolen. I purchased a used one off ebay. I received it, only to find it was bootloader unlocked, rooted. Not an issue in theory but I wasn't told that. Ok, upon trying the phone it worked but the battery would last 3 hours, it would have random reboots and would run so hot i could hardly hold the phone. I figured it was a faulty kernel. I flashed a new kernel and stock rom. Battery life went back to almost perfect but was off by about 20%. The random reboots were still an issue, but everything else seemed to work. A randomly rebooting phone is far from ideal. I figured I'd keep trying. Maybe it was a software issue. I would get random results with different roms. And the rebooting really seemed to occur when I had all my apps downloaded. So, I decided to run to flash again and run lean and see if with just the default apps whether it would reboot. After the flash, I waited a few hours, then BT and WiFi just stopped working. No go. The actual toggles revert to off position essentially immediately and neither turn on. I've since tried FDRs, different roms, different kernels, no luck. No idea what to do at this point. It could be hardware, obviously. It could be that the wifi chip was faulty and causing the overheating/battery drain from before, and finally after running so hot that one day before I flashed, it just did final damage to the chip that came to pass 3 days later. I don't know. It's possible but i somehow feel like it's a SW issue. I could send it back but it's complicated and i would really prefer to see if I can get this resolved. I've reflashed the modem bin files of stock roms, etc. Another issue i get often is when i try flashing, I get the writing 'boot'... (bootloader) Preflash validation failed FAILED (remote failure) and other such failures. Additionally, TWRP often just disappears. Aside from that, the OS, usually runs fine. I can't download apps obviously due to no WiFi, but everything else seems fine and I haven't had any reboots since the wifi/bt stopped working. I don't know if it's a partition issue, or hardware or what. I could use some advice. I'm at the limit of my patience and my knowledge here.
Let me know what you guys need and thanks ahead of time for your help.
Click to expand...
Click to collapse
What image are you using? Make sure you are using MPH24.49-18-4 (the -4 is important and newer than the one that ends in 18-18 on Moto's site) with the May 1, 2016, security update from here and flashing each step manually using this post's instructions.
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
If I am way off base, then it is likely a hardware problem.

acejavelin said:
What image are you using? Make sure you are using MPH24.49-18-4 (the -4 is important and newer than the one that ends in 18-18 on Moto's site) with the May 1, 2016, security update from here and flashing each step manually using this post's instructions.
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
If I am way off base, then it is likely a hardware problem.
Click to expand...
Click to collapse
Well, first off thanks a lot for your help. I had installed that particular version, though it wasn't the one currently installed. But I followed all the instructions and steps and got success writes for all and it booted up but didn't recognize any wifi networks and i tried to toggle on the wifi and same as before. Nothing happens. Wifi simply won't turn on. Same for bluetooth. Looking more like a HW problem isn't it?

vijn said:
Well, first off thanks a lot for your help. I had installed that particular version, though it wasn't the one currently installed. But I followed all the instructions and steps and got success writes for all and it booted up but didn't recognize any wifi networks and i tried to toggle on the wifi and same as before. Nothing happens. Wifi simply won't turn on. Same for bluetooth. Looking more like a HW problem isn't it?
Click to expand...
Click to collapse
I mean I know HW can die at any time, and maybe it was already dying from before which caused the initial issues when I got the phone, but I just have this sneaking suspicion that it's not HW related. I can't shake that feeling. But every SW based solution I try doesn't seem to do the trick.

acejavelin said:
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
Click to expand...
Click to collapse
Actually when u have a chance, I'd love this. Been rooting, modding my phones for years but I've never gone past a certain level of understanding. I'm not by nature a code guy though I have enjoyed playing around with custom roms and stuff. Anyway, ya, no pressure and my priority is to see if I can get this fixed or should just send it back, but if you do have time afterwards, would love to know what the deal is.

Still hoping someone can help me out with this. Any ideas? I'd really appreciate it.

vijn said:
Still hoping someone can help me out with this. Any ideas? I'd really appreciate it.
Click to expand...
Click to collapse
us the restore to stock tool, then install twrp and flash trupure and without booting flash the updated modem

unitz0mbie said:
us the restore to stock tool, then install twrp and flash trupure and without booting flash the updated modem
Click to expand...
Click to collapse
Hmm. Definitely willing to try that. You wouldn't happen to have links to Trupure and the updated modem would you? And the Restore to stock tool is this I assume: CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162. Not sure what Trupure is. It's a custom ROM?

vijn said:
Hmm. Definitely willing to try that. You wouldn't happen to have links to Trupure and the updated modem would you? And the Restore to stock tool is this I assume: CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162. Not sure what Trupure is. It's a custom ROM?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc

unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
That's so weird. Never heard of that before but will definitely try it. Thanks a lot.

unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
And Trupure? That's a ROM I assume. Know where I can find that? I could research it obviously, but figured there's likely a couple different versions of it. Would rather get the one you recommend. - nevermind. I see that the link you provided was for trupure. Thanks a lot. Will let you know how it goes.

unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?

vijn said:
That's so weird. Never heard of that before but will definitely try it. Thanks a lot.
Click to expand...
Click to collapse
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
vijn said:
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
Click to expand...
Click to collapse
what version of twrp are u using
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
vijn said:
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
Click to expand...
Click to collapse
try using the restore to stock tool, it will remove twrp
and then u can reflash twrp

unitz0mbie said:
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
what version of twrp are u using
Click to expand...
Click to collapse
3.0.2 i think. can't really check but i think that's what i remember from the last time i loaded it

Here's the thing, there seems to be a consistent issue writing to the boot partition and TWRP never lasts. I don't know all that much about this but I feel as though there's a part of the software that is constantly being deleted/overwritten and that may explain why the modem never stays and twrp never stays. Does that make any sense?
The return to stock tool gives the following 2 errors:
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.378s
and
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 149.569s
Obviously the second error is the end of the process. Can't go any further if it can't write the system. Super confused. Every time I install a new ROM another issue pops up.

unitz0mbie said:
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
what version of twrp are u using
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
try using the restore to stock tool, it will remove twrp
and then u can reflash twrp
Click to expand...
Click to collapse
Managed to get the restore to stock working. Restarted bootloader. Tried to flash twrp, and same error: writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.779s

vijn said:
Managed to get the restore to stock working. Restarted bootloader. Tried to flash twrp, and same error: writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.779s
Click to expand...
Click to collapse
is your bootloader locked?

unitz0mbie said:
is your bootloader locked?
Click to expand...
Click to collapse
to be honest, I don't even know any more. I've locked and unlocked it a bunch of times. Some tools I've used automatically lock or unlock it. At this point i just tried to unlock is using my key and got the following error: error: Command length (142) exceeds maximum size (64). So, ya, i have no idea what's going on. The bootloader page says device:locked, but the prebootloader page says bootloader unlocked.

unitz0mbie said:
is your bootloader locked?
Click to expand...
Click to collapse
I have to step away for a couple hours. I will be back. But regardless of how this goes, I just wanted to say thanks for trying to help with this stuff. I've never had so many issues with a phone before. My previous ones would occasionally give me some headaches, but not to this extent. Anyway, hopefully you'll still be around when i get back or will have some other recommendations.

sounds like your BL is locked man.

Does anyone try root Android 11.

Any advice apriciated.

I actually have been trying to get it to work since yesterday. Short version is, I personally cant get it to work, and it appears there are others who have had the same problems...
I will share what I have been doing so far....
- Updated to Developer Preview on Pixel 4 (that was a giant pain in the a$$ but that story is for another time)
- Installed current stable release Magisk Manager.
- Pulled the Boot Image from the 11 Dev Preview and patched with stable magisk version 20.3
Magisk log did say that it was successful, however my phone disagrees.
- Flashed newly patched image to Pixel 4 device.
Received the following output from SDK Tool:
Sending 'boot_a' (30436 KB) OKAY [ 1.290s]
Writing 'boot_a' OKAY [ 0.259s]
So all seemed successful, but...
- Device continued to bootloop back into fastboot and bootloader over and over again with a message about "no valid slot to boot"
- Did some searching, and found a thread here on XDA (sorry, not sure which one) where someone went into detail about how to flash the boot image to all slots.
- Used that info to attempt to reflash to all slots.
Command for flashing all slots from a Mac is:
./fastboot flash boot (Insert location of your magisk_patched.img) --slot=all
This did its job and I got the following output:
Sending 'boot_a' (30436 KB) OKAY [ 1.100s]
Writing 'boot_a' OKAY [ 0.396s]
Sending 'boot_b' (30436 KB) OKAY [ 1.100s]
Writing 'boot_b' OKAY [ 0.263s]
Finished. Total time: 3.490s
Thought I conquered this beast of an issue. I did not.
Even though it seemed like it may have worked, I ran into the same bootlooping. This is when I researched teh Magisk side of things and found the following "issue" from the magisk github repo.
https://github.com/topjohnwu/Magisk/issues/2477
Basically it is some other people who are having the same issue and some others who have pointed out that the developer (TJW) prob will not be doing any work on the dev preview at this time (which makes sense since it will change drastically).
And thats where I left my attempts at rooting 11.
Since then I just reflashed the original 11 boot image and got everything back to working again. Will probably go and find the canary build of magisk later tonight and see if that works, but for now, no real progress.

If you read his updates on Twitter (here), you can follow the progress that he's making.
Currently there is no working Magisk for Android 11, but he's working on it. Since there's a lot of code to refactor, I think we will see a working version in several weeks, so for now there's nothing to do except waiting

if only the devs for my few (gotta have ) apps would make them not require root access.
As usual XDA you've saved my butt from a lot of time wasted......

Jonathanpeyton said:
if only the devs for my few (gotta have ) apps would make them not require root access.
As usual XDA you've saved my butt from a lot of time wasted......
Click to expand...
Click to collapse
First, I would guess that if you have some "gotta have" apps, there are plenty of other people that also enjoy those apps. With enough demand, I assure you that there would be plenty of "non-root" alternatives available on the Google Play store if the features you want are actually available without root. If there aren't any "non-root" alternatives available to you, that should be the biggest clue that root is required to make the apps work the way you want. It's not the Dev fault that their apps require root. If you want to blame someone, blame Google for the way they structured Android.
Second, the current Android 11 release is specifically geared towards developers to start making sure their apps are compatible with the future release of Android 11. The fact that you want to install the developer release (which is a pre-beta release ) as your daily driver is your choice, but you should expect flaws, glitches, and bugs. You certainly can't ***** and moan about how certain functions (like root) aren't working for you - you will get zero sympathy.

Did the same attempt at rooting a Pixel 3 XL with Android 11, ended-up in boot-loop no matter which slot I used. Only flashing back stock boot.img worked.
And like you I ended-up on a similar page explaining Magisk does not work on Android 11 (for now hopefully).

3c said:
Did the same attempt at rooting a Pixel 3 XL with Android 11, ended-up in boot-loop no matter which slot I used. Only flashing back stock boot.img worked.
And like you I ended-up on a similar page explaining Magisk does not work on Android 11 (for now hopefully).
Click to expand...
Click to collapse
Yeah same for me today. I managed to get TWRP installed on Pixel 2 XL but no luck with Magisk.
I will subscribe to this thread and see when a Magisk version will work on 11.

Hi, Magisk Canary works on Android 11. I download the beta 1 zip and root via patch and flash the boot.img un the zip
Sadly, don't works with the beta2 because I actualize via OTA and patch and flash the boot.img of the beta2 stuck in fastboot