Hi all,
I think I just toasted my Nexus 7 3G while trying to upgrade the radio/bootloader, but before I toss it in the trash I wanted to see if many someone had any ideas I have yet to try.
Thanks in advanced to anyone who can help me!
The Problem:
Nexus 7 wont boot and is stuck on the Google logo with the unlocked bootloader icon. Cant boot to boot loader using Power + Volume Down. When I do Power + Both Volume Up and Down the screen goes black after showing the Google logo and my PC detects the device but cant find drivers and dont get anything out of fastboot commands. Power + Volume up does nothing.
Because the unlocked bootloader icon I doubt I could get away with sending it back.
What I did:
I was running CM10.1 with Bootloader unlocked
I installed the following 4.3 ROM - http://forum.xda-developers.com/showthread.php?t=2381991
Rebooted <-- Everything was fine but running on older Radio/Bootloader
I started following the following instructions to upgrade radio + bootloader - http://forum.xda-developers.com/showthread.php?t=2175086
I used TWRP to install the Recovery zip
Rebooted to bootloader
Fastboot Flashed bootloader
<<Forgot to Flash Recovery>>
Rebooted <-- everything was working
Rebooted to bootloader
Fastboot Flashed Radio
Rebooted << TWRP launched instead of stock recovery
Rebooted to bootloader
Fastboot Flashed bootloader
Fastboot Flashed recovery << Did not reflash recovery zip first >>
Rebooted <-- seemed ok
Rebooted to bootloader
Fastboot Flashed radio
Rebooted <<No Recovery Showed Up>>
Stuck with Google logo with unlocked bootloader icon and cant get back into bootloader
Hi Mazeri,
I having the same issue as I explained in the original thread.
I was flash the bootloader recovery and radio. Recovery and Bootloader flashes seemed to be ok but the radio flash run ok but when the n7 rebooted got stuck in the google logo.
I have tried all kind of key combinations with no success.
Here is the transcript of my flash commands:
Code:
~/Downloads ⮀ fastboot flash bootloader bootloader-tilapia-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.258s]
writing 'bootloader'...
OKAY [ 4.140s]
finished. total time: 4.399s
~/Downloads ⮀ fastboot flash recovery Recovery_Stock_Tilapia_4.3.img
sending 'recovery' (10240 KB)...
OKAY [ 1.223s]
writing 'recovery'...
OKAY [ 2.453s]
finished. total time: 3.676s
~/Downloads ⮀ fastboot reboot
rebooting...
finished. total time: 0.020s
~/Downloads ⮀ fastboot devices
015d2XXXXXX0d fastboot
~/Downloads ⮀ fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
sending 'radio' (16384 KB)...
OKAY [ 1.943s]
writing 'radio'...
OKAY [ 4.760s]
finished. total time: 6.702s
~/Downloads ⮀ fastboot reboot
rebooting...
finished. total time: 0.020s
~/Downloads ⮀ fastboot devices
~/Downloads ⮀ fastboot devices
How do you detect the device in your pc? What command are you running?
Im on a mac os x. If I do a fastboot reboot recovery, I get a 'waiting for device' message but there is no information for any combination of key presses.
If you are on a PC, have you tried any toolkit? I've read in a couple of thread that Wug's toolkit have worked to unbrick some devices with issues with the bootloader.
All I did was hold power until the screen goes black, then press and hold both volume up and down. The Google logo shows up and then the screen goes black. Windows then detects a device... but is unable to install a driver for it and it shows up as an unknown device.
Mazeri said:
All I did was hold power until the screen goes black, then press and hold both volume up and down. The Google logo shows up and then the screen goes black. Windows then detects a device... but is unable to install a driver for it and it shows up as an unknown device.
Click to expand...
Click to collapse
Also, I tried with the Nexus 7 tool kit and it failed to detect ADB. Fastboot also does not see the device.
Wug Toolkit also does not seem to work as it requires ADB or Fastboot to be working.
If I could get the device driver to kick in that might work... but something we did while flashs is making the device show up without details such as no device name and no mfg info... so Windows just shuts it down and calls it unknown.
I've got the same prolem Wug or Nexus toolkits cannot detect my N7 .... hix
I just flash the radio and my N7 stuck at Google logo....
amakaru said:
I've got the same prolem Wug or Nexus toolkits cannot detect my N7 .... hix
I just flash the radio and my N7 stuck at Google logo....
Click to expand...
Click to collapse
Maybe we should check what do ourt n7's have in common... It's strange that the flash worked for other n7 but not for ours.
Maybe that radio file is intended for certain devices (?).
Mine is a EU Nexus7 3G bought in early January this year. I guest is in warranty yet but because of the unlock icon in the start screen, the warranty is void
But I think this is not a problem related with the bootloader since the google logo appears and the unlock icon (so the n7 bootloader detects that it is unlock).
The flashing worked with the bootloader but it crashed when the radio was flashed for the three of us, so it is something related with the baseband. The OS installed should not be related since the bootloader and radio baseband are independent from the OS (Maybe you can get a soft brick, stuck in the colored X logo but bootloader should work).
I'm going to try to work finding a solution... but personally Im not feeling very optimistic
Now when I use three button (hold down power & vol + & vol - ) my computer show in device manager : "Android devices/ASUS Transformer APX Interfaces"
Sorry to say, but unless you can get your devices to fastboot mode, I think you're out of luck. It sounds like it doesn't get completely into the bootloader, which is problematic.
It was discussed a while back, and APX mode is a programming mode, but we lack the proper drivers and software to be able to recover anything on the N7 from that. Sorry.
I have a US Nexus 7 3G, got it right when they went on sale.
ameinild said:
Sorry to say, but unless you can get your devices to fastboot mode, I think you're out of luck. It sounds like it doesn't get completely into the bootloader, which is problematic.
It was discussed a while back, and APX mode is a programming mode, but we lack the proper drivers and software to be able to recover anything on the N7 from that. Sorry.
Click to expand...
Click to collapse
Bummer news :'( but I was expecting as much. If we don't find a fix, can we replace the main board to fix or is this problem beyond that point? Don't think selling a bricked device is worth it unless we have 0 options.
adb/fastboot commands
Another one bites the dust.
I should have followed the thread more closely. One of the steps (noticed this after the fact) is to "fastboot reboot", unfortunately this does not reboot the bootloader.
I should've noticed this yesterday after the initial fastboot reboot when I flashed the recovery image. Anywho, I believe the last step after flashing the radio should be "fastboot reboot-bootloader" not "fastboot reboot"? Maybe someone with more adb/fastboot experience could verify? Thanks.
bootloop after radio update!!!
my nexus 3g is from poland!!!
please, help!!!
Still no update guys, and no luck also
Right now I am thinking we will need to replace the main board, but I want to get that confirmed before buying a replacement.
I think that radio and bootloader must flashed first before upgrade to 4.3 . I do that with my N7 3G and now it works fine
my radiobands for device is for Poland Region
i hate myself
the only way is to flash radiomodule via APX, i have installed drivers, but have not .cfg and other parameters to flash Nvidia chip.
sambistt said:
my radiobands for device is for Poland Region
i hate myself
the only way is to flash radiomodule via APX, i have installed drivers, but have not .cfg and other parameters to flash Nvidia chip.
Click to expand...
Click to collapse
There isn't a place to know the parameters or whatever we need?
What can we change physically (motherboard, or any specific chip) to solve this problem?
If we return it to Asus or Google can it be repeaired? How much does it cost? Assuming the warranty is void because of the unlock icon..
---------- Post added at 01:25 PM ---------- Previous post was at 12:31 PM ----------
eternal70 said:
I think that radio and bootloader must flashed first before upgrade to 4.3 . I do that with my N7 3G and now it works fine
Click to expand...
Click to collapse
That was not the reason. I didnt upgrade to 4.3 before flashing the bootloader and the radio and I got the same result. The bootloader is not connected to the OS, but the OS is connected to the bootloader. I mean that it doesnt matter the OS in order the bootloader to run. But maybe it is possible to have the n7 soft bricked if the bootloader installed is not compatible with your OS.
Softbricked is when you are stuck in the OS logo (in case of the stock version is the colored X). This is very easy to fix, just runt in fastboot mode and flash the new OS and that's all. Everyone has experienced this situation eventually.
Our n7 are hard bricked. This mean that the bootloader or the radio (or both) are corrupted or bad flashed. In our case is the radio band (since we can see the google logo that is the bootloader). The weird thing is that while the bootloader is running (we can see the google logo and the unlock icon), we can't enter in the fastboot mode. Since we cant put the n7 in fastboot mode then we cannot flash anything (not os, not radio, not bootloader).
For now, the only way to flash bootloader and radio chip of the n7 is via APX. the problem is the APX configuration to flash the nvidia chips has not been released (as far as I understand, correct me if im wrong), so there is no way to know how to do it.
The only hope is changing this chips physically. Because everything is integrated, that means to change the motherboard, my guess (you can find tutorials in iFixit). What's the downside? The motherboard is basically the N7 so if you change it you change everything (the storage, the 3G, etc). You can check for motherboards in ebay easily just with search: Nexus 7 Motherboards. Range price varies from 20$ for 8GB to 140$ for 3G . Another question is if we can put a 8GB or 16 GB motherboards in our 3G N7, but I think so... it would not be a problem.
Everything I said a personal opinions and I can be wrong, so correct me if I'm wrong.
I have to say, I still have a very very very little hope that could be a fix for this, since we can see the google logo. But I'm thinking in ordering a 8G motherboard just in case
i`m thinking to give my n7 3g to my brother for parts and never buy tablet anymore, only ultrabooks.
My brother had the same problem and he managed to flash 4.2.1 with the nexus 7 toolkit.
The device got back to life again and then took the 4.3 OTA.
Sent from my Galaxy Nexus using xda app-developers app
There isn't a place to know the parameters or whatever we need?
Click to expand...
Click to collapse
no and never`ll be
easyflash only for transformer pad
i think to easy buy new nexus 7 2 gen or never buy tablet anymore
347 $ in trash
the new PS4 console is selling ~ 399$ - i think, it better to purchase new console that tablet
---------- Post added at 01:52 PM ---------- Previous post was at 01:44 PM ----------
DomieMic65 said:
My brother had the same problem and he managed to flash 4.2.1 with the nexus 7 toolkit.
The device got back to life again and then took the 4.3 OTA.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
really? your brother flashed radio module?
sambistt said:
no and never`ll be
easyflash only for transformer pad
i think to easy buy new nexus 7 2 gen or never buy tablet anymore
347 $ in trash
the new PS4 console is selling ~ 399$ - i think, it better to purchase new console that tablet
---------- Post added at 01:52 PM ---------- Previous post was at 01:44 PM ----------
really? your brother flashed radio module?
Click to expand...
Click to collapse
I don't know. Sorry.
I just mentioned this in case it may give you a clue.
I will ask and report.
Sent from my Galaxy Nexus using xda app-developers app
I just bought a Belsee Tesla style Android head unit with PX6 (double din, 1980*1080, 4G, 32G)
After installation for about 1 h, and I changed the boot logo to a new high resolution one. Then it did not work, stop at boot logo
The seller has send me a px6_format zip file and let me put it into a disk, plug the disk and restart the unit to recovery. But this method did not work. The unit kept at logo with no reaction.
I also tried many other method to try to enter recovery mod, but no luck.
Who can help me with this? Happy to pay for it! Thanks
pictures of this unit attached
ibb.co/z225dCS
ibb.co/StL3zwS
ibb.co/SvCYCzx
ibb.co/4FdgX4r
Did you try use a pin to reset the unit?
Also, where did you plug in the USB with the new update PX6 zip?
Try to put it in the USB slot on the unit, not the two from the connection cords.
JohnnyMHo said:
Did you try use a pin to reset the unit?
Also, where did you plug in the USB with the new update PX6 zip?
Try to put it in the USB slot on the unit, not the two from the connection cords.
Click to expand...
Click to collapse
I've tried every method, but no luck.
I removed the core board, and post it to the seller for an exchange. Then it works again. But the radio now cannot find any channel.
Terrible head unit, strongly suggest every one do not buy this type of trash.
After hitting a pothole my unit turned off and the OS never booted again. Still, I could apply updates but always got stuck in a boot loop.
I've tried sending it to a repair shop but they totally ruined the "vol" and "rx" terminals and now can't even get into recovery mode. There's a thread by marchnz about PX5 units where he describes how to transfer firmware by enabling OTG, by wiring a usb cable directly to the pin header.
Does anyone have the header's pinout for this model?
I tried contacting Klyde through AliExpress but they only instruct me to try updating it.
Hi is there anyone on these forums that can repair one of these chinese units
I have one of these https://www.ebay.co.uk/itm/384770479698 in my 2006 Merc. its a MTK8667 Android 11 based unit. FF_866X is the device name, i'm sorry I do not know the MCU
I was sent some update files from the seller https://we.tl/t-UeDC40i6Ul XRC-8667 升级软件 Q腾实UI多合一-国外-1280x720_v32_20220223
during the update process it copied the superimage ok but then something came up in red but it came up to a kind of recovery and said erasing... it then rebooted it gets to the car logo screen, before android screen then goes to a blank screen with the following in bottom left corner...FASTBOOT MODE and wont go any further
I have pressed RST then two fingers on screen until i get "detected" but all i get is the same fastboot mode again,
I have redownloaded and extracted the firmware and reformatted my usb drive to fat32 and tried the whole process again and tried in both usb slots but no sucess.
I have obtained other mtk8667 firmware files 8667.bin and 8667.upd from this topic https://forum.xda-developers.com/t/firmware-junsun-v1-8667q-8g-128g-vhd-qled.4405475/ on this forum but I have tried many different ones and it just wont read the usb, still just goes straight to fastboot mode....is anyone able to help me I have messaged the seller but no reply
So far I have tried about 7 or 8 different firmware versions, the sellers own, some junsun versions, ossuret versions even xtrons versions(all in correct format of 8667.bin and 8667.upd on root of usb formatted to fat32 but it does not read the usb.
The usb slots are still working as I can plug my phone in and it charges but the unit does not seem to have a full recovery mode
I have tried using a program called adb and fastboot on the computer but will not connect to the head unit
I have manually installed MTK drivers to the computer and tries a program called magic thunder but again would not connect to the unit.
I have tried to find a memory dump online but nothing, all I can find for mtk8667 is firmware consisting of 2 files 8667.bin and 8667.upd
I have now removed the unit from the car so i tried removing everything but 1 usb slot and removing the power for 10 mins before powering up and attempting to flash again
So i think i'm in need of expert help, so i'm looking for a repair shop, or person that can take the unit and hopefully get it working, more than happy to pay a fair fee and to post it to you, or if you are within a couple of hours travel from Yorkshire(Leeds area) I will happily come to you