Database Info

[ROM] Custom Roms For the GoGear Connect 3 8Gb

as I have promised here is are the first 3 custom ROMs for the gogear connect 3 8gb. if there is interest i will work on a few ROMs for the 16gb version also.
The way of installing roms on this device is a little different than most people are used to so i have included instructions
(with pictures this time!) but because of this way to do it it also makes this device almost brick proof and easy to fix.
before we start make sure your battery is at least charged 50%
THIS WILL DELETE ALL OF YOUR DATA EVEN THE STUFF ON THE "SD CARD"
In this guide i will be using the AndroidGeneric Rom for the example.
be sure to look in the rom package to see if i have given any extra instructions for the specific rom
1. Download the MfgTool Package at the bottom of this post. also download the rom package you wish to install.
2. extract the MfgTool Package somewhere onto your computer
3. extract the rom Package somewhere on your computer also.
4. now take the actual rom folder (in this case the AndroidGeneric folder) and put it into the profiles folder in MFG tool folder
5. Turn off your MP3 Player Compleatly
6. now with your player still turned off hold Volume Up and plug it into your computer.
7. dont let go of Volume Up untill a new device named SE Blank ELVIS shows up on your computer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. install the driver located in the Drivers folder inside the MfgTools Folder (the driver isnt signed so you have to click a popup allowing it to install, x64 users may need to turn off driver signing to get this to work)
9. After Thats Done open MfgTool.exe
10. once Mfg tool is open click on the Options drop down menu from the menu bar and click Configuration
11. in the window that pops up Select the USB Ports tab. then scroll down the menu untill you find "Freescale i.MX51 USB BulkIO Device" and put a check mark in the check box next to it. then select ok.
12. now your back to the Mfg tool main window. Check the Profile drop down menu to make sure it is on the rom you want. then hit start.
13. it will install the rom you selected. when you get to the part where it says "please connect device" and the stop button is red it is done installing. hit the stop button and unplug your mp3 player from the computer.
14. turn on your mp3 player with its new rom. it may take a little bit longer than usual to start up but thats only because its for the first time.
15. you are done unless there are more instructions with the rom.
for people that have already done this, here is a set of instructions to install differant roms
1. extract the rom Package somewhere on your computer.
2. now take the actual rom folder (in this case the AndroidGeneric folder) and put it into the profiles folder in MFG tool folder
3. Turn off your MP3 Player Compleatly
4. now with your player still turned off hold Volume Up and plug it into your computer using the same usb port that you used the first time
5. dont let go of Volume Up untill you hear the beep of the computer recognizing the device.
9. After Thats Done open MfgTool.exe
12.Check the Profile drop down menu to make sure it is on the rom you want. then hit start.
13. it will install the rom you selected. when you get to the part where it says "please connect device" and the stop button is red it is done installing. hit the stop button and unplug your mp3 player from the computer.
14. turn on your mp3 player with its new rom. it may take a little bit longer than usual to start up but thats only because its for the first time.
15. you are done unless there are more instructions with the rom.
Here Are the Files:
MfgTool
Download
Custom rom AndroidGeneric with root and all the gogear modifications removed and the regular android files installed.(regular android boot screen also) (radio app is from original rom)
Download
Original Rom with Root
Download
Original Rom With Root and all the bloatware removed
Download

Do I need to be rooted already to follow these steps or it doesn't matter?

you dont need to be rooted this can be used as an alternative to rooting

thanks for the guide im rooted running stock rom minus bloat that u uploaded

im working on a pretty cool ROM. ill release it when i get all the bugs out. it will be completely different from the roms i have posted so far. im working on a mix between the honeycomb blue accents and ipod touch styling with the page transitions form ICS.and custom fonts. im using the MUIUI Music app to give it a mor ipod touch feel. when im done testing the rom ill post it up here for you guys.

at this moment in time i am unable to continue in develpoment on the device i had to sell it because of some financial issues. i will post the rom i made as it stood the day i sold the device. it was a pretty good rom and it was pretty straight foward. i will post it online within the next few days

I have a 16GB version and would love to install a custom ROM on it. Please count me ad interested in getting a 16GB version. I am also running a 64bit Version of Windows, does your guide support this, or only 32bit systems?

thanks! this gogear is my first android device.. i am currently running your -bloat rom. i would like to create my own roms. i was wondering though how is it you create these rom?? is there a tutorial somewhere about this?

Thank you for creating these ROMS. Can you confirm what build they are based off of?
The latest build from Phillips is:
Android Version: 2.3.3
Kernel Version: 2.6.35.3-00054-g1e2e42c
Build Number: GGC3.01.06.10
I am guessing that your builds are based off of these, but would like to make sure before I flash something. (This is good info to have in the OP in some form.)

Have one coming
When I get mines on the 12th ogf february i may see if i can make roms

HGStone said:
thanks! this gogear is my first android device.. i am currently running your -bloat rom. i would like to create my own roms. i was wondering though how is it you create these rom?? is there a tutorial somewhere about this?
Click to expand...
Click to collapse
you need a linux computer and the android sdk to develope and the adb drivers installed.

After following this guide, my GGC became bricked
MfgTool would stop at "Formatting op6 partition" before showing me "Update error -65535-" and after unplugging/plugging back in it shows up as "Linux File-Stor Gadget" and I can't access it from Windows because it says "Please insert a disk into drive X:" (I changed the drive letter so I wouldn't get confused)
It turns on but doesn't get past the Philips logo. I tried repairing it with songbird but I always ends with an unexplained error.
I tried flashing it with mateo1212's OriginalRooted and AndroidGeneric roms as well as the original GGC3 rom found in C:/Program Files/Philips/Philips Songbird Resources/Firmware/SA3CNT/SA3CNT.zip (extracted the archive to MfgTool/Profiles and named it SA3CNT) and still no luck, ending in the same error mentioned above.
Can anyone help? Philips is already sending me a replacement (I played dumb with them) but if I could save this one it would be great...

Can anyone help me with this? I`m doing everything as the instructions say, but the MfgTool wont update the rom.
It starts working on the device, but gets stuck on error message (operation time out). After that it starts all over by itself.
One possible reason could be that the mfgtool version provided here was not working properly on my win7 (64bit). To solve this I downloaded another version of the program form the authors website.
The reason I had to change version was that the mfgtool crashed everytime I entered the "configuration" menu and the "usb ports" submenu.
All the help is much appreciated!

yep
superkidmax said:
After following this guide, my GGC became bricked
MfgTool would stop at "Formatting op6 partition" before showing me "Update error -65535-" and after unplugging/plugging back in it shows up as "Linux File-Stor Gadget" and I can't access it from Windows because it says "Please insert a disk into drive X:" (I changed the drive letter so I wouldn't get confused)
It turns on but doesn't get past the Philips logo. I tried repairing it with songbird but I always ends with an unexplained error.
I tried flashing it with mateo1212's OriginalRooted and AndroidGeneric roms as well as the original GGC3 rom found in C:/Program Files/Philips/Philips Songbird Resources/Firmware/SA3CNT/SA3CNT.zip (extracted the archive to MfgTool/Profiles and named it SA3CNT) and still no luck, ending in the same error mentioned above.
Can anyone help? Philips is already sending me a replacement (I played dumb with them) but if I could save this one it would be great...
Click to expand...
Click to collapse
same man

superkidmax said:
After following this guide, my GGC became bricked
MfgTool would stop at "Formatting op6 partition" before showing me "Update error -65535-" and after unplugging/plugging back in it shows up as "Linux File-Stor Gadget" and I can't access it from Windows because it says "Please insert a disk into drive X:" (I changed the drive letter so I wouldn't get confused)
It turns on but doesn't get past the Philips logo. I tried repairing it with songbird but I always ends with an unexplained error.
I tried flashing it with mateo1212's OriginalRooted and AndroidGeneric roms as well as the original GGC3 rom found in C:/Program Files/Philips/Philips Songbird Resources/Firmware/SA3CNT/SA3CNT.zip (extracted the archive to MfgTool/Profiles and named it SA3CNT) and still no luck, ending in the same error mentioned above.
Can anyone help? Philips is already sending me a replacement (I played dumb with them) but if I could save this one it would be great...
Click to expand...
Click to collapse
Hi,
I also want to change rom but after reading you, I'm afraid now.
Have you take a look to this thread: http://forum.xda-developers.com/showthread.php?t=1396085
It says on the first post that:
I Have Figured out how to unbrick and flash this device if you have Messed it up while having root privileges. this method can also be used to install custom roms once some are made. if people need the repair/flash method or wanna work on roms let me know in the comments and i will post the files and guides needed for it.
Click to expand...
Click to collapse
Good luck.

I am new to this forum and normally would not dream of rooting so I have printed the instructions and thoughly read them. I wish to use the Original ROM rooted and with bloatware removed. I understand the instructions except for step 8. How do I install the driver?
Anyone know why some people report failure and bricked devices? I would hate for this to go wrong!

Where is everyone?

GraySan said:
I am new to this forum and normally would not dream of rooting so I have printed the instructions and thoughly read them. I wish to use the Original ROM rooted and with bloatware removed. I understand the instructions except for step 8. How do I install the driver?
Anyone know why some people report failure and bricked devices? I would hate for this to go wrong!
Click to expand...
Click to collapse
Hi, just follow the guideline it will be ok, as to step 8, in the device manager you should right click the SE Blank ELVIS and manually install the driver, wait a moment it will successfully install the driver, after that you can follow next step.
By the way, I just flashed under Win7 64, everything went smoothly when just follow the guideline. Thank you mateo1212!

For people with bricks because of this
PPl don't be scared if you get bricked, i try at first and i got bricked, my device was in a loop and did not start, at the beginning just was showing a black screen then i tried to turn it on and it was in a loop.But i manage to recover it! This is what i did to recover it:
Download the mfgtool provided in this post.
Download the android files to flash provided also here
Put the device in flash mode or whatever is called the state when you power on the device with the volume up key pressed. ( for me this was specially hard since it was doing a loop, what i did was to push the reset button with a needle, then as soon as release the reset, push the power button and the volume up, and then connect the usb cable... create your own way to do it, just keep in mind you need to have your device booted in this kind of service mode ( vol up and power) before proceed.
Then just click on start and wait... it did it successfully this time...
Obviously you need to put your rom folder in profiles and everything just as explained in this guide.
THANKS, I UPDATED MY DEVICE WITH ROOT! :cyclops:
---------- Post added at 05:48 AM ---------- Previous post was at 05:41 AM ----------
GraySan said:
I am new to this forum and normally would not dream of rooting so I have printed the instructions and thoughly read them. I wish to use the Original ROM rooted and with bloatware removed. I understand the instructions except for step 8. How do I install the driver?
Anyone know why some people report failure and bricked devices? I would hate for this to go wrong!
Click to expand...
Click to collapse
In my case it failed just after it erase everything with no reason, however the same method worked the second time so i think is not risky to try, you are going to be able to install it eventually following this method. For more info see my other post. Cheers.

fail to root it by supper click try download flash
I try to use supper click to root it but failed the information is like below
step #7 WaitForDevice ................short name = mixed, utf8, errors = remount-ro)/dev/b.
any idea about it?

Flash the Android Market Voice search to Zeki TB1082B,TB892 & TB782B and no need root

Flash the Android Market Voice search to Zeki TB1082B,TB892 & TB782B and no need root
I just release a TB782B 4.0.4 ROM (non wipe ROM) in the below link.
http://forum.xda-developers.com/showthread.php?p=31186466#post31186466
You can found the way to unbrick your Zeki
http://forum.xda-developers.com/showthread.php?p=35259281#post35259281
Flashing the Android market for Zeki TB782B & TB1082B and no need root
(******Important Notice: Your tablet battery level must be over 50% when flashing the update.zip)
I have search the Chinese links and found the way flash the Google Market to the A10 Chip which is apply in Zeki TB782B and no need to root the tablet.
The steps
You need a micro SD card insert to the Tablet TF Card Slot
If you download the update.zip file from PC
1. Download the attached update.zip
2. Connect the Tablet with the USB wire to the PC USB prot
3. Go to Tablet USB mass Storage Screen and tap on the (Trun on USB Storage)
4. Goto your PC My Computer you will find two new disk, one is Zeki disc
5. copy the update.zip to the root the new disk of the micro SD in the tablet (Don't copy to the Zeki
Disc)
6. Goto Set UP
7. Goto About Tablet>SystemUpdate>Check Now>OK
8. The tablet reboot and go to the recovery screen
9. The recovery finish and power on again
10.. You will get the Google Market. Enjoy it.
Download the Update.zip with the Tablet
1.Tap the update.zip file and it will start to download the file
2 When the file finished download open the Es explorer
3. Tap SDcard download folder and you will find the update.zip file
4. Long Tap the update.zip file and a list jump up
5. Tap on the copy to and another list will jump out
6. Tap on the uppest row name /sdcard and with jump to another page
7. Tap on the /mint/extsd and tap to lowest row OK then the file will copy to the micro SD card
8. Follow PC download steps from 6 to 10
I can get the google market from the above steps if you can't, don't blame me!!!!!!!!!!!!!!!!
If you like it give me a thank!
Many request to add the voice search.
Here you are the update file for voice search(1.9mb).Extract the voice search file with 7z and file a update file in the voice search file. Follow the Market installation steps.
Somebody can't play the Temple Run game and it is because the G-sensor not tweak.
You can download the FID BN G-sensor Tweak file and extract it and get the update.zip file.
Follow above step to flash the file.
G-sensor Tweak file Warning :Be-Careful the G-sensor Tweak file is only good for the TB782 version which the back cover mark FID :BN (beside the Made In China)
Don't flash to other version and it will corrupt your G-sensor
Someone claimed in other link getting Google play download error.
follow the below steps
1. Open the Settings app.
2. Tap Applications.
3. Select the All tab.
4. Locate and tap Google Services Framework.
5. Select the Clear data button.
6. Tap OK on the warning that appears.
Although you may not have to, try restarting the device, then try to use Google Play. You should now have no problem downloading apps.
Thank FiOS Dan

Download and try!

My unit was rooted out of the box. NICE!

Set-up
I have done steps 1-5. 6 says go to set up and I'm not sure what you mean by go to set-up. Sorry if I sound dumb but I'm not sure where to go to go thru set up.
I GOT IT!!

does this need CWM or stock recovery
ok folk im on my second zeki. one the 1st one attempted to put CM9 on it after installing cwm. tablet booted to a sputtering white screen . i tlet the battery die then (vol - and power) to boot into recovery but encounter the same results. eventually the screen stopped coming on completly no matter what. I exchanged it at Sears for another.
Now without install CWM i attempted to do this market install. Similar result black screen and unresponsive. Are these things duds or did i miss something

worked for me
thanks man, it worked for me. this little tablet is great for the price. Too bad this is the only thread anywhere for the zeki.

Have to say this is a sweet little tablet for not much money. I had a little trouble flashing Google Play on, but it was my lack of familiarity with the device and nothing else. Here are some notes in case you need a little more detail than the OP furnished.
1. Charge and power up the device.
2. Install the apps per the leaflet that comes in the box.
3. Open the book reader app and spend a little time with the user manual. It helped me get familiar with some of the buttons and icons that differ on Android 4 from previous versions.
4. Insert a suitable micro SD card.
5. Go to Settings -> Storage and delete everything on the card to clean it up (if necessary).
6. Download the update.zip from the OP in this thread to whatever computer you're going to connect the device to.
7. Connect the USB cable. A USB Connected message should show up in the notification bar at the bottom and the USB symbol should appear.
8. Tap the USB symbol in the notification bar. A message should come up that asks if you want to turn on USB storage and explains that tapping the botton provided will let you copy files to the SD card.
9. As the OP says, two drives will appear. On my system, neither was identified as ZEKI, but one contains a folder named DCIM which is where the camera stores it's files on the SD card, so you know that's the right one. (You can check the properties of each if you want to to check overall size.) Copy the update.zip to the root of the drive with the DCIM folder.
10. You can then eject the device from the computer and let it remount the SD card.
11. On the device, go to Settings -> About Tablet -> Check for update -> Check Now and OK.
12. The device will restart in recov mode and you may see a path error scroll by at the bottom. In any case, the choices appear at the top and one will be to install the update from the SD card.
13. Use the volume rocker (up/down) to highlight that choice and tap the power button to select it.
14. At this point the device installed the update and rebooted.
When all was said and done, Google Play showed up in the app list and it even updated Flash and a couple other things. I used the same Google Account I have on my smartphone. I tried installing a couple of paid apps I have on my phone and it let me with no problem. I'm still playing, but it's pretty much all good so far. - MarkC

Thanks for the write up - I saw one of these at Kmart for $99 (also at sears) and thought it might be worth a try - they have a 30 day return anyways if it sucks.... Did anyone else get cm9 running on it?

Well - I went and bought one - looks waaay better than the 70's style Chino-clunker cheapies anyways. Went to best buy first to check out what they had (pantec and the supernova on sale for $150 (both the same price).. anyways here's what it looks like.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm itching to try a new rom on this thing, but not quite sure where to start - besides getting CMR on it first. Judging from the screen shot - does it look familiar to anything that might be compatible ROM wise?

I thought in the description on the Kmart site said that it charged through usb port, is the picture above the Zeki 7in tablet. Can you charge through usb? thanks
"Mini-USB port for battery recharge" -kmart

Charging options
The tablet comes with the wall plug with proprietary connection, but you should be able to use the USB cord attached to your computer as well. I have not tried this yet, but it is stated.

Yes - both ports show charging, but the manual recommends charging via the wall wart port.
Sent from my TB782B using XDA

Ozark_8125 said:
Yes - both ports show charging, but the manual recommends charging via the wall wart port.
Sent from my TB782B using XDA
Click to expand...
Click to collapse
charging current in usb port is lower than wall plug and take longer
---------- Post added at 05:35 PM ---------- Previous post was at 05:22 PM ----------
driedrice said:
ok folk im on my second zeki. one the 1st one attempted to put CM9 on it after installing cwm. tablet booted to a sputtering white screen . i tlet the battery die then (vol - and power) to boot into recovery but encounter the same results. eventually the screen stopped coming on completly no matter what. I exchanged it at Sears for another.
Now without install CWM i attempted to do this market install. Similar result black screen and unresponsive. Are these things duds or did i miss something
Click to expand...
Click to collapse
try install after factory reset with the tick on clean SD card
---------- Post added at 05:57 PM ---------- Previous post was at 05:35 PM ----------
Ozark_8125 said:
I'm itching to try a new rom on this thing, but not quite sure where to start - besides getting CMR on it first. Judging from the screen shot - does it look familiar to anything that might be compatible ROM wise?
Click to expand...
Click to collapse
don't try it the bootloader is lock. it will brick the table.
---------- Post added at 05:58 PM ---------- Previous post was at 05:57 PM ----------
Ozark_8125 said:
I'm itching to try a new rom on this thing, but not quite sure where to start - besides getting CMR on it first. Judging from the screen shot - does it look familiar to anything that might be compatible ROM wise?
Click to expand...
Click to collapse
Don't try it .The bootloader is lock. it will brick the table.

again for good measure dont attempt a rom install or even CWM install on this.
I've bricked 2 zeki tablets already.
in other news i gave up on this thing for now hoping a nexus tablet is really in the works. Would reather put $100 towards that.

Or if I can find a good deal on CL for a used kindle fire or nook color - lots of scam listings on CL for the kindle fire in particular.

Thanks for the additional , clear instructions. After three failed attempts it finally worked. For whatever reason I had to completely clean minisd card. Everything works great so no need to ROM !

efsres mifflin
The bootloader is NOT locked. I got CM9 installed on it, but the display drivers did not work. well the display worked, but no touch screen or rotation. I had to use a USB kb/mouse to use it.
I tried building a stock ROM through the extraction process, but never could get it to work properly. It would fully boot, but after about 10 minutes, the screen would always turn green and crash.
There are other threads, including disassembled photos of it on freaktab, but since I have not posted 10 times here, I cannot post the link.

Thank you very much it worked for the zeki , but when i go to Google play music or amazon music i am unable to play audio samples , but used pandora and that is able to work ... can someone help

I have tried this many times now and stil cannot get it to work. Google Play(market) and the other apps in the zip file do not automatically load after the update and if I try and load them manually from the zip file on the extsd card then the market will continually crash. Not sure what I am doing wrong and any insight would be greatly appreciated.

[SOLVED] Nexus 5 stuck in boot loop animation (Lollipop) , partially working with 4.4

I have a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
One day, after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images.
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it was crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it was useless.
I took the phone to an LG lab. They said I need to replace the motherboard. Costs about 200$ !!
I was about to get a new phone , but decided to try one more google search for a fix.
This guide is for any poor soul in the same state.
This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount.
I found out by trying to follow this guide: http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist".
This is a software problem.
Her's how to fix it (It's a long and detailed guide - but worth the result):
First, you must enable USB debugging mode , if it was not enabled (if it is enabled you can skip the first step of this guide) . The way to do that is to flash a stock image that will load, even if not fully working. In my case I could flash version 4.4x and get the phone to load. I am not aware of any other way to enable USB debugging, other than from within a working OS. If someone knows a way - please post it.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, it should load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new Developer Tools and enable usb debugging. Approve any popups.
*** I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.****
Next, you need to have ADB on your PC, and it should be able to reach your phone. If you already have - then skip to the next step. If you don't - then here is how to get the latest version:
Go here and download the installer https://developer.android.com/sdk/index.html#Other
Install the file and when it's done run SDK manager. Choose only the first 2 tools (Android sdk tools and Platform tools), this will install the latest adb and fastboot tools. To make sure all is installed open a command prompt (Click Start, type cmd in the search and run cmd.exe) and type adb. You should see all the adb possible commands typed. Now you can test if your phone can be reached by adb: connect your phone (remember usb debugging must be on!) and type: adb devices. After a few seconds you should see something like this:
List of devices attached
024703f599cc8feb device
If you get this, it means you have usb debugging enabled and a proper usb driver installed and you can go to the next step . If there is no device in the list you need to install/update the USB driver:
You have to make sure that when you connect your phone with USB debugging on, you have 2 entries in Winodws Device manager:
Under Portable devices >Nexus 5 , and under Android device> Android composite ADB Interface.
If the second one is missing, ADB will not work and you can't continue. There are 2 ways to fix that :
1. You can install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
The author of that guide states you need to uninstall any driver that already exists. This proved tricky because Windows would not uninstall the Nexus 5 driver. I decided to install it on a PC that has no android driver.
When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
2. If that does not work or if you don't have another "virgin" PC try this:
Run SDK Manager, under Extras mark Google USB driver. You don't need anything else marked. Install the driver.
Now connect your phone to the PC in normal mode (not bootloader!) . Open device manager. You should have two entries: Portable devices >Nexus 5 and Android device > Android Composite ADB Interface
If the second one is missing, but the Nexus 5 is properly installed, Right click on the Nexus 5 device >Update driver software > Browse my computer for driver software >Let me pick from a list. Now make sure that "Show compatible Hardware" is ticked . You should now have an entry called "USB composite device". Choose that and let it install. When it's done, if you still have an an Unknown device >Nexus 5 and no Android Composite ADB Interface in device manager, then unplug the phone and reconnect it again . You should now have both devices installed.
If by chance this does not work, and you have a Nexus 5 with a yellow error , right click it>update software driver> Browse my computer.> and point it to the Universal Naked Driver folder or the SDK>Extras>Google USB driver folder and it should update so both devices appear (Nexus 5 and ADB).
Once adb can see your pohne go here, to read bitdomo's guide to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work:
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode to be turned on, and the proper usb driver installed.
Second, you need to install a custom recovery image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Last, you need to root your device. There are many ways to do this. I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
I did not follow the steps for the wifi and BT fix , because they worked fine (and still do 4 months later) , but you can go ahead and do that too.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device. Done! Boot up the device and make sure it recognizes the right amount of RAM on your phone (16 or 32GB). If it does, then all is well .
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .

stuck at unlock step
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad

Thanks! Helped me to save my N5!
Do not need to exactly as it is posted but the directions is good!
Thanks again.

killian.1140 said:
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Click to expand...
Click to collapse
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck

Or just read the stickies.

I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers

Thank you so much for this! You saved my phone!

volvoxxda said:
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Click to expand...
Click to collapse
But for that you have had to install TWRP in the first place...
Mine was stock.
Where is the backup saved?

Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..

volvoxxda said:
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
Click to expand...
Click to collapse
Flash drive? Do you mean the Nexus internal memory?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
External, like on this picture.

Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue

volvoxxda said:
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
Click to expand...
Click to collapse
Did you just replace the button or did you have to replace something more?
Thanks

Just the button. You can DIY, it's easy.

worked
worked great. confusing in the start but got it working. Thanks for a life saving guide for nexus 5

incredible
Hi eross,
I registered and logged in just to say thank you for this amazing tutorial. I've been trying to repair my N5 for about 12 hours, and I was about to give up when I saw this post. You saved my Nexus!!
Thanks again. :victory::highfive::good:

eross said:
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Click to expand...
Click to collapse
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T

ambervals6 said:
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
Click to expand...
Click to collapse
You can try to download the stock firmware that's installed on your phone and flash the recovery img, or flash twrp recovery.

help
eross said:
This is a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
Yesterday after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images. (can't post links yet...)
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it is crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it is useless.
I am wondering if it is a software or hardware problem. It appears as though part of the phone's memory is not functioning . Is there a way to check this? Is there a way to fix this?
Thanks
Edit: Just came back from an LG lab. Bad news. Need to replace the motherboard. Costs about 200$ !! Can't find anything cheaper on ebay. Guess it's time for a new phone
Edit #2 - SOLVED !!:laugh:
OK, this for any poor soul in the same state. This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount. Here is how I found it out, and how I fixed it:
First, try to flash a stock image that will load, even if not fully working. You will need this later. In my case I could flash version 4.4x and get the phone to load.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, if you are lucky it will load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new developer tools and enable usb debugging. Approve any popups.
I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.
Once this is done , boot the phone into debugging mode.
Read the guide here http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist". I then understood what the problem was. If you get the same error - you are in luck!
Then go here, to learn how to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work.
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode.
Second, you need to install a custom recover image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Third, you need to install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
Since the author of that guide states you need to uninstall any driver that already exists, I decided to install it on a PC that has no android driver. When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
Last, you need to root your device. (I think this can also be done from within TWRP , but I am not sure how...) I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt where adb.exe is located , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device.
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
Addendum: According to bitdomo, installing a custom recovery like TWRP enables USB debugging by default even if the phone does not boot. I have not tried this myself, but this means you can foergo installing os 4.4x , and go straight to ADB and run the command that fixes the persist partition.
Go ahead and try it. It will save you a lot of time!
Click to expand...
Click to collapse
My N5 has exact problem as yours even same errors of camera and playstorw crashing when i loaded older android version.. now im positive your instructions will help me but im having some trouble with your steps i do not know how to type comnands with ADB .. im truly novice and dont want to damage the phone more could you simplify the steps or make a video please? Thank you

Sorry, I can't make it any simpler than that. I can't make a video now because my phone is fixed. Adb is very simple, it's like an old DOS window where you type the text. I would follow Bitdomo's advice and start by installing TWRP. This will get you USB debugging, and you can run ADB and follow his instructions to fix the persist partition.

Bricked after Downgrade to Pie, adb not working, pls help

[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any thoughts please?

I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.

akhilarora666 said:
type "Oneplus 7 Downgrade Firmware".
Click to expand...
Click to collapse
Thank you for your encouraging message.
That article you mentioned says this:
copy the Rollback package to the phone’s internal storage.
Go to device Settings > System > System Updates > Tap on top right icon > Local upgrade > Select the installation zip package > upgrade > System upgrade completed to 100%.
Click to expand...
Click to collapse
But as my screenshot shows, I am not able to boot, so how is that supposed to work?

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
akhilarora666 said:
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
Click to expand...
Click to collapse
That's not possible when you have no os anymore...
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
Just stay on xda-developers, no need for suspicious off site downloads.
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Or the unbrick tools: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325

who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
In my case, I was stuck too. So i did "fastboot boot recovery.img" tried both android Q and android pie revocery. (version 70 and 65) (editied versions by mauronofrio) one of them worked. I got into the recovery. then installed the android Q stock firmware zip file. Thing is, i dont know why, but once you are on android Q, your phone stops supporting android PIE. Since you were on android Q once, you have to go back there. only then follow the external website i linked.
Like the other guy said, you can stick to XDA and try the unbrick tools. but for me they didnt work. So i followed that website. then everything was fine. Ofcourse its fishy. but once you are back on pie, you can reinstall any pie rom you want.

strongst said:
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Click to expand...
Click to collapse
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)

who ah way said:
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
Click to expand...
Click to collapse
Your screenshot is the fastboot screen. Stated with: fastboot
If your device is not recognized, maybe you should check your adb drivers etc.

TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.

who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
Same situation happened to me but due to wipe in twrp vendor image

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
You used a nandroid backup which is what resulted in the brick. Nandroid backups do not backup firmware
Anyway try
fastboot --set-active=a
Then reboot and see if it boots
Or try
fastboot --set-active=b
If that doesn't work download twrp and flash it to the boot partition
fastboot flash boot whatever
Reboot and you should have twrp
Which twrp to flash? The one for Q firmware. It's obvious
---------- Post added at 22:31 ---------- Previous post was at 22:25 ----------
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
I do not know how you formatted cache on a device that doesn't have a cache partition

[MTCD/E] Android 10 upgrade using official Free tools

To upgrade a MTCD/E PX3, PX5, PX6 from Android 6+ on using official Rockchip free tools - a reminder, bringing together multiple threads.
First note - if coming from Android 6 - early versions of Realtek dual BT/WIFI (type 2) are not supported past Android 6.
[29/06/2020 - Android 10 - Users are report Bluetooth MD725 Type 1 is not working on Android 10...]
The only fix is to replace the wifi/bt module with the supported "type 1" GOC-MD-725. See this thread for details (placeholder)
Risk:
Also, there is risk associated in upgrading. The SDCard method is known to result in back-screen, sometimes recoverable booting to recovery from SDcard again. If this method fails, OTG becomes the only recovery option.
Two Rockchip Official methods;
A. SDcard Method
Note: To use these methods, your unit must support booting from SDCard or USB. Not all MTC variants are created the same, so test first.
The following is required for SDcard method
- (1) Full ROM in .IMG format
OR
- (1b) bootloader/recovery only image to flash recovery,
https://drive.google.com/folderview?id=11zpgoOW4eU6G1tjs7ExsZ2aC4RoZ9KDr
AND
- a 'full' OTA of your choice.
- Rockchip SDCard create tool
https://github.com/rockchip-linux/tools
1. Create SDCard using Rockchip SDcard create tool.
2. Insert and boot from SDcard, follow prompts.
3. Wait for install to complete...and can take some time
(1b) Flash boot/recovery image then an OTA zip. Thanks to @ikerg for recovery .IMG files.
2b. Create SDCard using Rockchip SDcard create tool with .img
3b. Insert and boot from SDcard, follow prompts.
4b. After flashing, remove SDCard, boot to recovery then flash an OTA from another SDCard or USB stick.
* Download bootloader/recovery flash image from here; https://drive.google.com/folderview?id=11zpgoOW4eU6G1tjs7ExsZ2aC4RoZ9KDr
B. OTG method - "Never fail, flash like a Boss, impress your friends method"
*May require Jig, or if lucky an USB A-A cable.)
The below method will recover a 'bricked' or non-booting unit.
If wanting to backup your ROM and test other ROMs, this is the method you want.
The following is required:
- ROM in .img format, or partiton extract
- Android Tool and Driver:
https://github.com/rockchip-linux/tools
1. Install Rockchip driver and Android Tool on PC/Laptop.
2. First try connecting your unit USB to USB using cable to PC. Try all headunit USB ports.
3. Try entering recovery. If successful you will hear the new device chime on your PC and the headunit will be connected.
If connecting via USB method does not work, a jig must be made. See the following thread for details: https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
4. Using Android Tool connected via USB - Flash SOM using .img file. If image file does not install, erase flash first after selecting .img file.
C. Downgrading steps here: https://forum.xda-developers.com/t/...ing-official-free-tools.4123933/post-85473141
Hope this thread clarifies the two free and official methods to upgrade your headunit. Enjoy.
29/06/2020 - Update - Users reporting MD725 - Type 1 Bluetooth is not working on Android 10.
28/07/2020 - Update - include bootloader/recovery plus OTA method from IMG files kindly created by the talented @ikerg .
29/06/2020 - Update - Users reporting MD725 - Type 1 Bluetooth is not working on Android 10.
March 2021 - Update - BT module found - HW upgrade to enable Android 10 upgrades. See my module thread.
August 2021 - SD Card Downgrade steps - from A10, A9 using A8 for success.
Note: Best, most successful risk free method - OTG

...placeholder...

In the other rom thread people reported black screens when trying to upgrade. I had the same issue. I used 2 SD Cards to successfully upgrade from Android 8 to 10.
With card 1: I created a SDCard using Rockchip SDcard create tool with the following ROM https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 10/CHS .
With card 2: I followed the instructions from [https://forum.xda-developers.com/showpost.php?p=79513558&postcount=2] section a) until point 10 / the video https://www.youtube.com/watch?reload=9&v=EhEdeD5RICk until 2:55. I then put SD Card 1 into the HU and pressed reboot in recovery. I then saw the Android 10 update screen. It took about 30 minutes to update, it then booted into Android 10.
The rom seems buggy. I'm not sure if its the upgrade method or the rom itself. I'l try to flash a different android 10 rom to see if it works any better. Worst case I can flash to Android 9 using card 1 / Malaysk ROM.
Hope this makes sense.

Harsesis said:
In the other rom thread people reported black screens when trying to upgrade. I had the same issue. I used 2 SD Cards to successfully upgrade from Android 8 to 10.
With card 1: I created a SDCard using Rockchip SDcard create tool with the following ROM https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 10/CHS .
With card 2: I followed the instructions from [https://forum.xda-developers.com/showpost.php?p=79513558&postcount=2] section a) until point 10 / the video https://www.youtube.com/watch?reload=9&v=EhEdeD5RICk until 2:55. I then put SD Card 1 into the HU and pressed reboot in recovery. I then saw the Android 10 update screen. It took about 30 minutes to update, it then booted into Android 10.
The rom seems buggy. I'm not sure if its the upgrade method or the rom itself. I'l try to flash a different android 10 rom to see if it works any better. Worst case I can flash to Android 9 using card 1 / Malaysk ROM.
Hope this makes sense.
Click to expand...
Click to collapse
Did you got the rom from here?
https://disk.yandex.ru/d/umCvHqCDzHccr/RockChip PX6 Android 10/HCT
Enviado do meu iPhone usando o Tapatalk

Nhokas said:
Did you got the rom from here?
https://disk.yandex.ru/d/umCvHqCDzHccr/RockChip PX6 Android 10/HCT
Enviado do meu iPhone usando o Tapatalk
Click to expand...
Click to collapse
I already posted which ROM I used. Not sure if it's special or you can use any Android 10 IMG file.

marchnz said:
First note - if coming from Android 6 - early versions of Realtek dual BT/WIFI are not supported past Android 6. The only fix is to replace the wifi/bt module with the supported type. See this thread for details (placeholder)
Click to expand...
Click to collapse
I have MD725 BT module, i think is type 1, never had problem with bluetooth before, from android 6, 8 and 9, and now with A10 is broken. Tried 3 different rom. So replace with what? I will downgrade to A9.

alt.d4c said:
I have MD725 BT module, i think is type 1, never had problem with bluetooth before, from android 6, 8 and 9, and now with A10 is broken. Tried 3 different rom. So replace with what? I will downgrade to A9.
Click to expand...
Click to collapse
There will be no way to get this module to run on Android 10. The best thing would be to replace the module.

A10 recognizes the MD725 module as BC6 but does not establish a connection.

I will try all the options listed in factory settings.

I installed A10 with the Boot-SD method, like i did with A6 and so on.
But it did not work like it has to. You have to manually go to the recovery. Inser the SD-card and then press reboot to sytem.
After that the install begun.
Now i am looking for a way to root A10.
Regards

zeyret said:
A10 recognizes the MD725 module as BC6 but does not establish a connection.
Click to expand...
Click to collapse
How was that identified? Do you mean if you set the module in factory settings to bc6? Or is that the output of a logcat/dmesg?
Could someone with a md725 type1 kindly export and attach dmesg and logcat from their android 10 upgrade?
I can then take a look and try to figure out what's going on. Really wish I had a second unit to mess around on, so I can try and figure out potential mods etc to fix this md725 problem.
I figured out the hardware mod to get working md725 on Android 6 on...but haven't had anyone willing to donate hardware (need a headunit, even without a SOM)

Hello thank you for this thread.
Just to be clear, flashing from sdcard an OTA file from android9 to android10 (without hal9k modinstaller) will result bootloop because recovery and bootloader are different ? am I right ? (I always did it with modinstaller)
Also what I did not know is flashing .IMG file will change bootloader and recovery with sdcard tool ?

ric69 said:
Hello thank you for this thread.
Just to be clear, flashing from sdcard an OTA file from android9 to android10 (without hal9k modinstaller) will result bootloop because recovery and bootloader are different ? am I right ? (I always did it with modinstaller)
Also what I did not know is flashing .IMG file will change bootloader and recovery with sdcard tool ?
Click to expand...
Click to collapse
You need the img file not the OTA

Android 10 Bluetooth MD725
marchnz said:
How was that identified? Do you mean if you set the module in factory settings to bc6? Or is that the output of a logcat/dmesg?
Could someone with a md725 type1 kindly export and attach dmesg and logcat from their android 10 upgrade?
I can then take a look and try to figure out what's going on. Really wish I had a second unit to mess around on, so I can try and figure out potential mods etc to fix this md725 problem.
I figured out the hardware mod to get working md725 on Android 6 on...but haven't had anyone willing to donate hardware (need a headunit, even without a SOM)
Click to expand...
Click to collapse
Hi @marchnz
Bluetooth MD725 and WQ_BC6 logcat / dmesg

I have Dasaita MAX6. I am trying to do SD Card upgrade method. With both 16GB SD and 4GB SD card, when I reboot from recovery, I just get black screen. Has anyone with Max6 gotten this to work? If so, what exactly were the steps followed and files used? I am trying to use this IMG: https://docviewer.yandex.ru/view/0/...wODEyNDcsInl1IjoiOTQ0OTU5NzE3MTU5MzUyOTkyOCJ9

graycorgi said:
I have Dasaita MAX6. I am trying to do SD Card upgrade method. With both 16GB SD and 4GB SD card, when I reboot from recovery, I just get black screen. Has anyone with Max6 gotten this to work? If so, what exactly were the steps followed and files used? I am trying to use this IMG: https://docviewer.yandex.ru/view/0/...wODEyNDcsInl1IjoiOTQ0OTU5NzE3MTU5MzUyOTkyOCJ9
Click to expand...
Click to collapse
Use 8GB or less SD card.

zeyret said:
Use 8GB or less SD card.
Click to expand...
Click to collapse
I did, I tried using a 4GB as stated. I did get it to work though. Used a different computer with a different SD card reader.

zeyret said:
Hi @marchnz
Bluetooth MD725 and WQ_BC6 logcat / dmesg
Click to expand...
Click to collapse
Hi, could you check the files - looks like these are all the same 1 kilobyte file - a MCU Configuration export - and not the actual logs

In my case, i have a 10,1 inch MAX6
This one has a GPS card slot behind the screen but in my case this is a fake GPS card slot.
But i knew there is a sd-card slot at the side of the head unit hidden behind the sheet metal.
So i opened the head unit.
Then you have to make a boot sd-card, manually boot to recovery, insert the sd-card and then boot to system and the system update starts.

so i have a question
there is img and ota files for PX6 on HCT folder
i will need the img file to do this
but can i use the ota afterward ?
and is HCT7 and HCT4 the same ?
https://i.imgur.com/fl8So7k.png