Related
I know. You guys have heard it all before...but
I was using WugFresh to re-flash back to 4.3 from 4.4 and the recovery was taking so long. After an hour of running, I was moving the device to a coffee table when the cable fell out.
Hay, why isn't a message include in WugFresh like the backup process as to approximately how long this process takes? That brings up another issue in general with these old N7s is that these micro-USB female connectors get loose after so many years of use, makes connecting and charging difficult.
But I digress.
I have read often in the XDA forums about a factory reset ‘from bricked feature’ in WugFresh, but I can not find that feature anywhere where ‘bricked’. anything is. If it is there, where is it?
Anyway, how can I recover the bootloader and everything without having to learn doing everything via a cmd line or .bat process?
These are the facts:
Nexus 7 2012, 8g, re-flashing back to 4.3 from 4.4, using Nexus Root Kit
v1.8.2, Flash Stock + Unroot (I had read in XDA Forum somewhere where it was suggested to go back to a factory vs to use this option).
The N7 is currently has one of 4 states available: Bootloader screen (with below stated status), Google initial screen (with "Start" Showing and "Booting failed" in the upper right corner), or it can Power off. Recovery Mode is an option, but does nothing but cycles to the Google initial screen.
In Fastboot mode the status says this:
FASTBOOT MODE
Product name - grouper (it got that far)
Variant - grouper
HU version - E3
LOCK STATE - UNLOCKED
Bootloader Version - N/A
Serial Number - 015d2109ab281807
SIGNING - not defined yet
Of course I can't get an MTP connection to Microsoft XP, but an "Unknown
device" error shows up under USB when I connect the cable. No drivers from WMSDK kit or any from WugFresh worked.
Oh, and by the way, the WugFresh backup didn't work for me. It saved next to nothing, but I have another type of backup that works, so no worry.
GOT ANY SUGGESTIONS?
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Click to expand...
Click to collapse
{Q} Thanks Captain, I have been following the Guide instruction, but I have some other questions before I proceed.
In your Quote above you said “follow the sticky for reflashing”, I don’t know what you mean by a “sticky” and I have looked though a lot of the pages after the "[GUIDE] Flashing a Factory Image with fastboot / return to stock" and I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Since I didn't know that answer, I went a head and read the whole Guide and other questions popped up: If I have to download Java SE JDK will the Version 6 I already have work? The Oracle website you directed me to won’t let me download Version 8; however, Android SDK did accept Version 6 to install.
I did re-download all the drivers as instructed and put the JWR66V bootloader into the place of the JWR66Y one and then inserted bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, and flash-base.sh all into <my sdk directory>\platform-tools as the Guide says.
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
I don’t know what you mean by a “sticky"
Click to expand...
Click to collapse
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top.
I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Click to expand...
Click to collapse
Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
Click to expand...
Click to collapse
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Now its Driver installation issues
Captain Sweatpants said:
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top. Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
{Q} Installing the driver now seems to be the issue. I tried a couple of things:
1. I know this was not exactly appropriate, but I went into Device Manager, located the USB “Unknown Device”, tried to update
the Driver after selecting it, directed the screens to both the ‘supposed’ drivers in WugFresh and Adb subdir’s. None took.
2. Then I forced a new device though the Control Panel’s, Add New Hardware, navigated to “Add a new hardware device” and
selected “Google Nexus 7 ADB interface”, and it created the new device. The Device Manager showed and error on the
device, so I refreshed it with the Adb driver, with no different results.
3. I then added the device driver “Google Nexus Bootloader Interface” via Add New Hardware
4. I rebooted the computer. After it came back up…
5. I looked at the Device Manager with no change in the status of any of the Android or the Unknown USB Device.
6. I insured the N7 was in bootloader mode by rebooting with volume keys/on key.
7. I went ahead and ran “adb drivers” cmd after entering the “cd’ cmd. I got the following:
Bear with me as I have no screen printing capability at this time.
>Command Prompt screen:
>C:\<adb dir>\platform-tools> adb devices
>List of devices attached
>C:\<adb dir>>\platform-tools>
And as you can see, NO listing showed.
So what’s next? I have another XP computer I can try this on, but I will have to get all the Abd stuff over to it 1st. While you answer I will try that.
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device.
Click to expand...
Click to collapse
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
nickynooner said:
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
Click to expand...
Click to collapse
It wouldn't work as I would need to be able to press buttons on the nexus.
If none of this is working then try wugfresh NRT again make sure you have the most up-to-date version from www.wugfresh.com its 1.8.2
The option you are looking for is unroot/back to stock there is an option for soft bricked make sure that is ticked
Sent from my Nexus 7
Hit thanks if I've helped
The Fat Lady Just Sang an Unhappy Song!
Hi Captain,
Thank you for all of your help and patience with me. I have read a lot more about the status of my device through looking at the XDA forum about other devices that have the kind of issue I do, and I have concluded mine is HARDbricked. I went ahead and ordered another motherboard off of eBay. My device was an 8G and I got a 32G replacement, making sure it was for my age of my N7. XDA forum and other websites say the boards are interchangeable. I was thinking about buying a new device anyway and this way I can upgrade and still have the same familiar device with no learning curve of a new one.
Hello all,
As one can ascertain from the title, I have my Nexus 7 "Razor" (2013) edition stuck in a boot loop, with it not able to be recognized in adb.
Now before you mob me for not making a recovery, I didn't expect when flashing an official google image to go wrong. Well, clearly, that didn't happen. Some notes that may help you in assisting me:
The bootloader is unlocked.
Originally usb debugging was enabled, however, with the current lack of OS, it appears to be gone/reset.
I am a semi-n00b with with this stuff, but I can understand about 80% of directions, nevertheless, take it easy please
Thank you for any and all help!
A. You are in the 2012 forums.
B. USB debugging only applies to a booted OS. In fastboot mode it is not needed. What image did you flash and how did you flash it?
#stayparanoid
Oh my apologies, I am a noob.
I was trying to flash the android L dev preview.
Sent from my HTC One using XDA Free mobile app
Okay, so after countless attempts to d everything and anything turning my computer on and off did the trick... However flashing l eventually was another story. Thanks for your help. Idk how to officially close this thread though.
Sent from my Nexus 7 using XDA Free mobile app
Hey guys! Im really busy rite now and don't have time to search through the threads but maby yalls can help me quick. I broke the screen of my razr m and got a new fone but now I have to use it again. I fixed the screen and it's working but battery is completely crap. I use it all day and the charger doesn't keep up.. not playing games either just music and Whatsapp . Also it crashes and reboots 5 times a day. I did the SEEM edit and am using it on GSM. Any ideas? Are any custom ROMs better?
Are you using an OEM Motorola charger? What's your average battery life? What's your system version? Have you checked your battery stats to see what was using the battery? How long did the device sit with the battery dead prior to the screen replacement? The reboots may be due to using it on GSM if your on KitKat... Please provide additional information and we'll be happy to assist you the best we can.
We cannot teach people anything; we can only help them discover it within themselves.
ezknives said:
Are you using an OEM Motorola charger? What's your average battery life? What's your system version? Have you checked your battery stats to see what was using the battery? How long did the device sit with the battery dead prior to the screen replacement? The reboots may be due to using it on GSM if your on KitKat... Please provide additional information and we'll be happy to assist you the best we can.
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
OK the system version is 183.46.10 Verizon.en.us. No I think the charger quit.
The average time on battery is about 4hrs. It sat for about 3 months but it was fully charged to start with. What does GSM have to do with KitKat? No haven't tried the battery stats app. And any audio app is screwed up (like voxer and WhatsApp voice messages) like the apps just lock up. I rooted now do the cosyom ROMs support gsm??
Ok looks like im bricked. Tried to unlock bootloader and no luck.. tried to downgrade and no worky and now its stuck in fastboot cant do anything. All flashing fails and i dont have a fone now...
zike47222 said:
Ok looks like im bricked. Tried to unlock bootloader and no luck.. tried to downgrade and no worky and now its stuck in fastboot cant do anything. All flashing fails and i dont have a fone now...
Click to expand...
Click to collapse
You can't downgrade a locked bootloader. Definitely will result in a soft brick. You're going to need to flash back to the STOCK version that you were last on (looks like 183.46.10?) Go to that website I linked, download that firmware and flash it using either Sam's RSD Flasher or House of Moto/. Both of those topics have DETAILED instructions that you must read to have a successful flash. I personally use and love House of Moto.
xKroniK13x said:
You can't downgrade a locked bootloader. Definitely will result in a soft brick. You're going to need to flash back to the STOCK version that you were last on (looks like 183.46.10?) Go to that website I linked, download that firmware and flash it using either Sam's RSD Flasher or House of Moto/. Both of those topics have DETAILED instructions that you must read to have a successful flash. I personally use and love House of Moto.
Click to expand...
Click to collapse
Ok i have RSD lite installed so i will use that and see if i can recover it. Any idea why the bootloader unlock didnt work?
edit: it says `failed flashing unknown fastboot command` ideas?
edit: deleted var get -var lines and we are running again.. i want to flash a custom rom tho so want to unlock BL..
zike47222 said:
edit: deleted var get -var lines and we are running again.. i want to flash a custom rom tho so want to unlock BL..
Click to expand...
Click to collapse
Go for Towelroot+Motocalypse in order to unlock BL. Then flash a custom recovery and flash all the ROMs you want.
Or, if you still want to downgrade, or if you are aware that some ROMs based on the KK BL have bugs, you can downgrade AFTER you have unlocked BL. Follow the guide in the General section.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
AndyYan said:
Go for Towelroot+Motocalypse in order to unlock BL. Then flash a custom recovery and flash all the ROMs you want.
Or, if you still want to downgrade, or if you are aware that some ROMs based on the KK BL have bugs, you can downgrade AFTER you have unlocked BL. Follow the guide in the General section.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
Ok i got bootloader unlocked by just installing Motopocalyps apk. But now i cant get a recovery installed!! I havnt ever used command prompt before for that. And they say to extract.. how would u extract a .img file??
zike47222 said:
Ok i got bootloader unlocked by just installing Motopocalyps apk. But now i cant get a recovery installed!! I havnt ever used command prompt before for that. And they say to extract.. how would u extract a .img file??
Click to expand...
Click to collapse
Search for how to use / download mfastboot. You won't want to soft brick your device by messing with fastboot commands.
Boot into bootloader. Connect to PC.
Command:
mfastboot flash recovery ***PATH-TO-YOUR-RECOVERY.img***
..and you're done.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
AndyYan said:
Search for how to use / download mfastboot. You won't want to soft brick your device by messing with fastboot commands.
Boot into bootloader. Connect to PC.
Command:
mfastboot flash recovery ***PATH-TO-YOUR-RECOVERY.img***
..and you're done.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
Ya I searched and found all that but still can't get it to work. Everything works until the flashing like the computer identifies the fone but won't flash. I must just be getting the path wrong.
Try rashr or flashify and ensure you grabbed the correct recovery
We cannot teach people anything; we can only help them discover it within themselves.
Im trying to build cm13 unofficial from source i downloaded and im following this guide: http://xda-university.com/as-a-devel...id-from-source
And i used this guide to get source code and some others downloaded: https://nathanpfry.com/how-to-setup-...-android-roms/
Im using openjdk 8.
I got it to compile and it said "done" but when i flash the rom.zip it gets stuck at manufactor logo. i did not install anything else. thats all. ideas?
Phone is Nexus 4 8GB MAKO.
Bump
You're going to need to get some sort of logs to troubleshoot such as dmesg or kmsg. Unfortunately in order to get that without being able to boot the rom and enable root/developer mode settings, I believe you will need a modified kernel.
Sent from my SM-T350 using Tapatalk
Koognod said:
You're going to need to get some sort of logs to troubleshoot such as dmesg or kmsg. Unfortunately in order to get that without being able to boot the rom and enable root/developer mode settings, I believe you will need a modified kernel.
Sent from my SM-T350 using Tapatalk
Click to expand...
Click to collapse
Ideas where to find that?
You'd have to either make one yourself or find a developer who will do it for you. sorry I cannot help you more than that. here are a few more pages I found when googling https://android.stackexchange.com/questions/26123/android-boot-up-messages-for-debugging , http://bootloader.wikidot.com/linux:android:kmsg
could possibly be a reference
https://github.com/ResurrectionRemix/android_frameworks_base/issues/139
I'm trying to resume the discussion about the possibility to build a custom ROM for ASUS Z500KL P00I - Asus Zenpad 3S 10 LTE. I'll put together all the stuff I found about this argument, in the hope to find a way to give some more life to this nice piece of hardware.
I actually can't think of a reason it couldn't smoothly stand last Android 10, except maybe for issues in driver versions.
Of course I own one of those and I'm willing to do help the development.
Unluckily so far I didn't find anything about a custom rom, apart for some rumors about rooting and unlocking.
BOOTLOADER:
In another post I found someone that claims that the bootloader can be unlocked with the asus unlock tools apk, but in the last firmware versions it sais "the package conflicts with an existing package by the same name" and the apk won't install.
I tried with the unlock tool for the Z500M and I can confirm it won't install.
In another post I found someone that says the Z500KL bootloader can be "fooled" to flash self signed packages using fastboot in this way:
Code:
fastboot getvar sofia_support
fastboot flash boot boot_patched.img
I think this bootloader can be unlocked somehow, or it is possibile to flash stuff in some way. I don't think the bootloader is the issue here.
Posts:
https://forum.xda-developers.com/showpost.php?p=76322038&postcount=15
https://forum.xda-developers.com/zenpad-10/how-to/root-asus-zenpad-z10-zt500kl-zenpad-3s-t4067617
https://forum.xda-developers.com/zenpad-10/help/custom-recovery-rooting-z500kl-p00i-t3796558
RECOVERY MODE:
Found some posts where someone says the Z500M TWRP can work also for the Z500KL, but found others that say that they are completely different hardware.
I tried installing the official TWRP APP, but it seem it don't have the package for any zenpad at all. I did then some searching, but can't seem to find a link to a modified version either.
Also, looking at the bootloader, it don't say anything about a recovery mode. There is just a "Factory reset" entry in the fastboot menu.
CUSTOM ROM:
I found at the asus site the sources of an earlier version.
I'm used to compiling linux kernel and programs, but don't have any experience in compiling this stuff, or using the configurations and drivers in these sources to compile a recent version of android.
If is there someone that has news on this front or that has experience and it's willing to help I'll put my device and time to do tests and stuff.
Thanks
I wish there were some roms and I knew how to build lineage is for this tablet.
I wouldn't try a Z500M binary on Z500KL or TKL, the Z500M is a MediaTek SOC and the Z500kl is a Qualcomm.
I think the first step is TWRP.
saq-xda said:
I wouldn't try a Z500M binary on Z500KL or TKL, the Z500M is a MediaTek SOC and the Z500kl is a Qualcomm.
I think the first step is TWRP.
Click to expand...
Click to collapse
Hi, thanks for the info!
Do you have any hint on how to get a working TWRP for the Z500KL?
_payne_ said:
Hi, thanks for the info!
Do you have any hint on how to get a working TWRP for the Z500KL?
Click to expand...
Click to collapse
Trying to get it figured out, not familiar enough with Android internals to know where to go yet. AFAIK there is a switch somewhere to set bootloader lock off, I have root but not sure where that variable is stored ("set" commands from ADB root shell are not working). After that is done it is probably a pretty standard TWRP build. Too bad as it looks like a pretty nice tablet.
Handicapped by not knowing much about Android, but think of three possible attack surfaces from a rooted device (which we have now):
(1) Hacking an Asus unlock tool to send the Z500KL information to Asus - might work, depends on how much checking they do at their end for serial validity or if the databases for serial/etc. numbers are separate for the different models or not. If they're all together and it is a simple lookup command on their end this might work. Also possibly snooping in on the connection from another Asus device and see if we could "spoof" it without the app. Note that this is based on the hypothesis that the app calls out to Asus for a unlock code, there are other ways it could work.
(2) If as has been hinted Asus merely removed the "OEM Unlock" toggle from the menus then going through a rooted tablet and setting "by hand" might work. Depends where the toggle is located and if the bootloader will still recognize it. Per https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel it appears to be stored in TEE (Trusty) or FRP on Pixels, and . From a rooted device if you know the calls we should (?) be able to call Trusty to set the flag, or if we know where it is in FRP set it there. A post on XDA here from Dr. Mario points at the physical efuse partition and suggests it can be adjusted if we have root (which we do now) - https://forum.xda-developers.com/t/asus-zenpad-z10-zt500kl-verizon.3494106/#post-69674114
(3) There are hints and signs that perhaps Asus' signing verification chain isn't watertight - see https://forum.xda-developers.com/t/...-z10-zt500kl-and-zenpad-3s-10-z500kl.4067617/ and https://forum.xda-developers.com/t/custom-rom-for-z500kl-p00i-zenpad-3s-10-lte.4184773/ (comment on self-signed loaders), as well as possibly looking at the "user settable root of trust" option at https://source.android.com/security/verifiedboot/device-state.
I know that I flashed the Z500KL bootloader to a ZT500kl and installed Magisk. Tablet boots but gives the Android-recommended user root of trust warning screen.
If you need a custom ROM you can dig here, and you can also download LineageOS 16 here
Looks like nothing has happened here in a while. Am hoping for an update though if some progress ahs been made. I can't even unlock the bootloader so far... never mind find a ROM that works on it!
The reason I'm here is, I now find that even the ASUS apps are no longer supported on Android 7 (not that I used the ASUS apps much), but still... I looked on the firmware page and was really saddened by the fact that the JP version (which I have) had only 4 months of support (ie date from first firmware and last firmware is only 4 months apart...). For the WW version, it was 6 months. This is really a complete joke... It's a real pity because the hardware is not bad at all, and it is one of the last 4:3 screen ratio tablets. It's terrible to think that this thing has not had even security updates for the last 5 years, so unless I can get a custom ROM on there, then I think I'm going to have to look elsewhere for something.