yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
I'm confused. It's a little off-topic, but what does "restoring my data" have to do with TWRP in the context of flashing a new ROM?

Anyway, I would proceed with a dead battery or loose battery connector hypothesis first. It's not obvious why writes to /boot, /cache, /data, or /system would affect the bootloader.

Anything is possible at a low enough probability I suppose, but you should start troubleshooting operations with the high-probability scenarios first.

For instance - with the power off, will the "charging screen" display when you plug the tab in? How about APX** mode? (Plug in to PC and start with Power+Vol-up). If you didn't see either of those, it's likely a power supply or hardware problem.

good luck

** make sure you exit APX mode by holding down the power button for at least 20 seconds. I'm not sure if it shuts itself down after an inactivity timeout - you don't want to be draining power while trying to charge the tab.
[Nexus 7 Q&A, Help & Troubleshooting] frap129:
Well, you backup your data, Wipe data and cache, flash the rom, gapps, ect. then restore data, the charging screen wont dispaly, apx mode doesnt work, but the whole story: went to flash a newer version of my rom, install faills due to error in updater binary so i go to reboot and it says "No OS Installed! Are you sure you want to reboot?" i press dont reboot, go to install the older version of the rom, go to restore data and then it shut off.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
The lack of APX mode or the charger screen suggests a battery problem or a hardware failure, not a software problem. APX mode will be present even if the tablet has absolutely nothing in flash memory.

Having nothing in /system (no OS or even no filesystem) will not affect bootability of either the bootloader or the recovery.

I don't know why you would wipe data only to restore it after flashing a ROM. Usually wiping cache & dalvik-cache is sufficient for "dirty-flashing" a ROM upgrade as it is very unusual for ROM installs to diddle with the /data partition. (But making full backups is always a good idea.)

I would check (carefully) to see if the battery connector came loose before you decide to throw the tablet away.

good luck
[Nexus 7 Q&A, Help & Troubleshooting] frap129:
Battery connector didnt come loose, still dosent work. guess it might just be broken

EDIT: I plugged it in to my pc and the google screen came up for about 20 sec then it shut back off. havent been able to get anything since
[Nexus 7 Q&A, Help & Troubleshooting] Soldier 2.0:
Is it possible to enter Odin on the n7?
[Nexus 7 Q&A, Help & Troubleshooting] Pirateghost:
Odin is Samsung only

Sent from my Galaxy Nexus
[Nexus 7 Q&A, Help & Troubleshooting] sdelange99:
You can hold the power button for 10 seconds and wait till you see the Google logo. Then release and hold it 10 seconds again, when the screen turns off hold the volume down button and wait for it till it automatically boots again. You'll enter bootloader mode. Download wugfresh' nexus root toolkit and install it. When the program is loaded there is a flash stock option on the right side of the program. Select the soft brick / boot loop option under the flash button. While in boot loader mode connect your nexus and press the flash button.

This is all I know!
[Nexus 7 Q&A, Help & Troubleshooting] CarlKirshner1989:
NEXUS 7 Bricked - NO OS - tried everything but...

It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.

I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
[Nexus 7 Q&A, Help & Troubleshooting] Pirateghost:
USB debugging doesn't mean **** when you are in a custom recovery. It has adb already. Your problem is your computer. Fix your computer by following one of the bajillion threads and posts about the nexus 7 drivers issues.

Installing drivers does not need android to be booted.

Your best bet is to put it in fast boot mode and follow Google's own instructions to flash it back to stock.

Sent from my Galaxy Nexus
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
I must admit I'm a little 'hazy' myself when it comes to ADB related issues... I've never had much cause to use ADB. (Think I've used 'adb pull' on a couple of occasions). And I've never been in the invidious position of not having a bootable Android OS on my Nexus 7 either - which does seems to happen a quite lot with TWRP users, less so with CWM users.

Anyway... just had a tinker... and you could try the following workaround... this seemed to work to for me.

----------------------

Locate the folder on your PC where you keep your FASTBOOT and ADB .exe files...

Copy whatever ROM .zip you want into this folder.

The following example uses SmoothROM-v5.0.zip ... There is nothing to stop you from renaming this to something shorter, for ease of typing later... so, in my case, just smooth.zip.

Boot your Nexus 7 into the BOOTLOADER (Vol down [hold] + Power button), and then into RECOVERY (TWRP) and hook it up your PC.

Open a command prompt window on the aforementioned folder... and type...

adb devices

...which should yield something like the following...

List of devices attached
012345679ABCDEF recovery

(If you don't see a serial number... then you definitely have a driver problem...)

Otherwise, it's just...

adb push smooth.zip /sdcard

Or whatever ROM you wish to 'push' to the emulated SD card.

This will likely take a fair few minutes for a 300Mb+ size file (typically the size of your average ROM)... on my Windows XP box it took 4 minutes (1328 KB/s, 32565894 bytes in 239.486s) to copy over. And there are no 'progress gauges' of any kind, either... So season your patience:) a liitle. You can always pull up another command prompt window and type

adb devices

again to ensure you still have an ongoing ADB connection.

Once copied over, and still in TWRP, you can just flash it.

Good luck.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] frap129:
Still nothing on mine. im just about to give up and wait to see if google releases the N7 second generation at the i/o
[Nexus 7 Q&A, Help & Troubleshooting] xornibblovsky:
If You familiar with Linux, You can try to understand the logic of

changing the modes.

You need to run udevadm monitor in one terminal. Then press some

combinations of key/s and look for changes with usb-devices.

The better, if You run wireshark and sniff USB interface with your device.

Put attachment here, with a comments what was pressed.
[Nexus 7 Q&A, Help & Troubleshooting] frap129:
since it seems to be a hardware problem, not software, im just going to send it to asus and see what they can do.
[MDA II, XDA II, 2060 Accessories] remlap:
As anyone seen these on expansys yet

http://www.expansys.com/product.asp?code=113388&asource=106055

Seems really neat shame I dont have a XDA II or If I did have a use for it but dam that looks cool.
[Droid Incredible Q&A, Help & Troubleshooting] nykcmelo7:
I think i messed up my Inc, because i'm S-OFF running android 2.2 non-rooted. Is there any way i can go back to normal stock? I can't do an OTA update because i get a red triangle in the recovery.
[Droid Incredible Q&A, Help & Troubleshooting] Flagmax:
If you are S-OFF then flash cwm or twrp recovery using fastboot.exe Then flash stock or whatever rom using recovery.
[Droid Incredible Q&A, Help & Troubleshooting] lukkypuggy:
http://www.mediafire.com/download.php?5b7te3ra10d323n
[One (M7) Q&A, Help & Troubleshooting] ManBearPig618:
Hey guys - quick question, and sorry if this has been answered before. I did a quick search and couldn't find an answer under FAQ or recent threads. I apologize in advance for any duplicativeness. Here it goes:

I ended up getting my One directly through T-Mobile, so it's not the HTC developer edition or unlocked model. Once I unlock/root my "TMo" HTC One, will the ROMs under the "HTC One" dev forums work, or do I have to stick to the ones posted on the "T-Mobile HTC One" dev threads? Thanks in advance.
[One (M7) Q&A, Help & Troubleshooting] xXxG0dzRAgexXx:
They will work on your T mobile HTC One.

Sign up for Copy! A great dropbox alternative that gives you tons of FREE space! http://copy.com?r=luU4NP

Start off with 10 gigabytes of free storage with my referral!
[One (M7) Q&A, Help & Troubleshooting] ManBearPig618:
Do I need to do anything after flashing ROMs from this forum to "adjust " them to tmo radios or anything?
[One (M7) Q&A, Help & Troubleshooting] ManBearPig618:
Hate to shamelessly bump, but can anyone confirm this?
[One (M7) Q&A, Help & Troubleshooting] Shadow Samurai:
No, tmobile varients are supported on nearly any Rom out atm

Sent from the one and only HTC One
[One (M7) Q&A, Help & Troubleshooting] BableMan:
Have you seen those custom desktops, Like Stardock or Fences, that have widgets and functions you can't get in regular windows? This is far from 100% accurate but think of the rom as the skin over windows. Those never really effect your drivers(the radio) since they just tweak your GUI so as long as they can run on your hardware you'll never have to worry about them effecting your printer.

Does that make sense or is my brain fried from my self directed 36 hour crash course on this forum? :D
[One (M7) Q&A, Help & Troubleshooting] ManBearPig618:
Makes enough sense. I've only ever rooted/unlocked/flashed ROMs on Nexus devices, so I just want to make sure I know what I'm doing before I dive in here. Thanks!
[One (M7) Q&A, Help & Troubleshooting] shawman:
IDK about ARHD, but triuckdroid will ask you AT&T/INTL/T-MO before you flash, so everything works correctly. I believe all HTC Ones in the US(So Far) are the same as the INTL..... there's a thread about it somewhere.... But just make sure you have the right APN settings. P.S New radios are usually a good thing if you have bad signal all the time (WiFi/Cellular).
[One (M7) Q&A, Help & Troubleshooting] eakrish:
Has this been confirmed by anyone else?
[Miscellaneous Android Development] roshandes:
good project

i am in... :laugh:
[Miscellaneous Android Development] bucefal82:
We've done our best to deliver robust and delicious custom roms to our device (even using andrea or some other work [which are great], but, well.. android is opensource in the end :P).

We hope you could help us with cm development (mostly on kernel part).

At last it would be great to see some light in the mtk darkness..
[Miscellaneous Android Development] FenixxPl:
Hi,

I'm trying to start working on CM for MTK6589 device. (Star S7589)

Kernel sources (for normal Android) can be found (has been released by Acer few weeks ago), but the biggest problem is the "device" folder.

I've written e-mails to few producers (ZOPO, Cubot, THL), and even that I've gotten replies from ZOPO and THL, they don't want to share anything, nor the kernel, nor any other sources.

If you'll get to something, please post it here, or pm me, and if I'd make any step I'll also keep you informed.
[Miscellaneous Android Development] dmplot:
Maybe it would be a good idea to sign a petition to Lenovo to "open the source code for the device"? 4pda russian forum would participate in signing such petition. And I assume there will be much more other communities / forums where we can spread this information to join us!

There are two steps to do this:

1. What is a petition website preferrable for such action?

2. To prepare the text for the petition which would be technically correct and would cover all the aspects we are waiting from Lenovo.

Anyone to take responsibilities for any paragraph?

---------- Post added at 03:18 PM ---------- Previous post was at 02:50 PM ----------

As an example of petition I looked at the "Give us Ice Cream Sandwich for HTC Desire HD".

So, the petition site I think is chosen. It is http://www.ipetitions.com/

So, who will take care of technically correct statement for the petition?

There is one more issue: the channels for such information spread. As to my thoughts it might be:

1. xda developers (of course),

2. 4pda russian forum,

3. Lenovo russian forum,

4. Please propose more...
[Miscellaneous Android Development] Xado:
nice to see guys good if we get this working but any chance of mt6575 processors they are capable of running ics so cyanogenmod 9 ?
[Miscellaneous Android Development] Damag3:
This is great, i´m a ZTE v970 MT6577 owner and love the idea. I have kernel for ZTE Grand X V970 already uploaded to github and download the android sources and CM to start building.

The problem is im not a dev or have any kind of formation so I dont know if Im doing rigth. But i will try

I build a cm from scratch to my htc wildfire but I just had to do the steps of the CM tutorials.

Sorry for my inglish
[Miscellaneous Android Development] kthz:
Good luck to you guys, i was lurking on XDA just to search for a few optimizations for my MTK6589 phone (HDC). This quadcore cpu is spreading like wildfire among chinese phones due to its low price, so hopefully you will get some good help for getting started.
[Miscellaneous Android Development] tuancollection:
i'am hopi will custom rom ICS for my phone lenovo a690 mtk 6575,rom512,ram512:(
[Miscellaneous Android Development] FenixxPl:
Short update on the topic:

1. I've made working TWRP recovery for mine Star.

I had to rip it a bit (awfully small recovery partition), but it looks like it's 90-95% working, just without partitioning possibilities. (But backups/recovery of them fully works, as same as other TWRP functions, and offcourse it's all operated by touch.)

2. I've compiled CM10.1, but it doesn't start, so here there is really a lot of work in front.
[Miscellaneous Android Development] Xado:
hey guys I kinda ported cm7 on my mt6575 phone well I luckly got it booted up but only the thing was I was not able to go pass the lockscreen its some thing to do with some touch screen drivers only my power button worked any one know how to deal with the touch screen drivers ?
[Miscellaneous Android Development] nathan-96:
Maybe its better to start with CM9 or CM10, since Mediatek (ours) does not support JellyBean 4.2 yet. So getting CM10 on it would be freaking hard.
[Miscellaneous Android Development] ShadyGame:
I also have a mtk phone, i would like to run cyanogend on it one day, iam no developer, im just gonna sit back and watch :) good luck
[Miscellaneous Android Development] FenixxPl:
LPCRJ™ - Congrats! That's something, I'd say that even something really big, because noone else had even got to that point.

If you can, please share your sources (device/vendor catalogues) on github, then we'll be able to help you more :)

nathan-96 - Mine has got JellyBean (4.2.1), that's why i try to port the CM10.1, also I'm not sure if kernel 3.4.5 will work with CM9 and I haven't got any other to work on.

Still, mine CM isn't even going past first boot screen, even using hints from Lenovo P700 sources.
[Miscellaneous Android Development] nathan-96:
Sorry I thought you had the same mediatek processor as the op, but I read that you have one that, apperiantly, supports JellyBean 4.2. Its indeed a big step.

But we need Logcat's to see why its not passing bootscreen, because you might be closer than everyone's thinking right know.
[Miscellaneous Android Development] amardeepsingh77:
Xolo Q800 / Fly IQ446 / Gionee GN708W Kernel

Hi friends, I was able to get my hands on the kernel for Xolo Q800 / Fly IQ446 / Gionee GN708W Kernel which are essentially the same phone. They run JB 4.2.1 today, though the kernel is based on 4.1.2. Will this suffice or do we need anything more to get CM working.

http://yadi.sk/d/-zrdnTk_4Iy7c

All these phones are Quadcore MT6589 1.2 GHz processors with 1 GB ram and 4 GB flash. And, roms of these phones can run on each other.

Thanks
[Miscellaneous Android Development] FenixxPl:
amardeepsingh77 - You're my god!

There is literally everything in that source, the "device" catalogue, prebuilder scripts, complete kernel sources, it's kind of unbelieveable!

Now we are possible to really get to work, not just move in the dark :)
[Miscellaneous Android Development] Xado:
yo guys I was trying to port cm7 but I really wanted to port cm9 so I left porting cm7 because my phone is already running gingerbread here is a thread I found http://xdaforums.com/showthread.php?t=2246892 he have actually ported cm9 to mt6575 processor phone though I don't have this phone but I think porting to other mtk phone might become easy using his ways I flashed it on my phone but I had a bootloop I try editing stuff but no success. thanks to PdroidAndroid
[Miscellaneous Android Development] bucefal82:
It seems to me that for a start, and 9 will do.

For at least that is what I can bude customize.

Yes and no need for the device in 512 MB, 4.2.

Also, can anyone have an idea for $ agree to help?

Мне кажется что для начала и 9 сойдёт.

Ибо хоть что то буде что можно будет кастомизировать.

Да и не нужен на девайсах в 512 мб ,4.2.

Также есть идея может кто за $ согласиться помочь?
[Miscellaneous Android Development] FenixxPl:
Next update from the field:

However sources from amardeepsingh77 are awesome, it'll take a lot of time to succeed the build.

Our MTK devices can't be compiled like all others Android devices, because we can't simply use ./build/envsetup.sh, we've got to use makeMtk, and it's got a lot of annoying stuff.

Without that we can't build preloader, and without it I don't think any Cyan or other rom will work.
[8.9" Kindle Fire HD Android Development] Hashcode:
ATTENTION: PUBLIC SERVICE ANNOUNCEMENT

It has come to my attention that under certain circumstances when the Kindle HD's get stuck in a bootloader bootloop the information on the "boot0" block of the internal storage can be ERASED and RESET.

This partition is special and contains ALL of your device's hardware specific information:

- Wifi MAC address + Encoded Secret for registering w/ Amazon services

- BT MAC address

- Serial #

etc

FOR BACKING UP THIS PARTITION:

adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb pull /sdcard/boot0block.img

Place the "boot0block.img" file with the other files that you backed up in the original instructions for safe keeping.

FOR RESTORING THIS PARTITION:

(do not do this unless you are absolutely SURE that your boot0 block got wiped out -- hopefully you never need to)

This is done via adb from your PC while the device is in TWRP recovery or in the Android OS (not fastboot):

cd <your safekeeping files>
adb push boot0block /sdcard/boot0block.img
adb shell "echo 0 > /sys/block/mmcblk0boot0/force_ro; dd if=/sdcard/boot0block.img of=/dev/block/mmcblk0boot0;"

THIS FILE IS UNIQUE TO YOUR DEVICE AND CANNOT BE REPLACED OR REBUILT FROM ANOTHER DEVICE. DO NOT SHARE IT WITH ANYONE AS IT CONTAINS INFORMATION ABOUT YOUR DEVICE USED BY AMAZON DURING REGISTRATION.
[8.9" Kindle Fire HD Android Development] ryanhein:
I tried to backup my device's 0boot however,

I have no idea about why the KFHD (Cyanogenmod 10.1, your build on 11 May) cannot be detected with ADB devices command.

I have enable the Developer Options in settings menu and have both Android Debugging & ADB over network enabled. Any comment about this?

Thank you.
[8.9" Kindle Fire HD Android Development] apd:
Thanks Haschode - worked first time

Blimey - a little less aggressive would be good!

If adb is not recognising your device perhaps the drivers are not installed properly as it worked fine for me first time.

Assuming you have the android sdk installed, if you need help installing the drivers look at posts 7 and 8 in this thread.
[8.9" Kindle Fire HD Android Development] jonahy:
Im still on stock rom rooted has 2nd bootloader and CCW

try to back up but I got this when i try to pull

D:\sdk\sdk\platform-tools>adb devices

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

B0C9100425160LG8 device

D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"

D:\sdk\sdk\platform-tools>adb pull /sdcard/boot0block.img

remote object '/sdcard/boot0block.img' does not exist

Any thing i did worng? and boot0block.img is not in my sdcard folder

Thanks advance
[8.9" Kindle Fire HD Android Development] GSLEON3:
Depending on your setup & your environmental variable paths, you may have to launch the CMD window from your Android SDK folder. Depending on what version of the SDK you are using, it may be in platform tools for the older sdk, or in X:\Android\system\bin, where X equals whatever drive you installed the SDK on. It works from that folder every time for me & only sporadically from anywhere else.
[8.9" Kindle Fire HD Android Development] timnan:
Yes. Had same problem here.

I am on build 0511 at present and everything is good enough to me.

Since Hash reminded all of backup for one more image 0boot recently. Then I tried to connect to pc in ADB mode so I can backup it and push it to my pc in OS windows7. The enviroment for adb was good because I used same computer and system to install the second bootloader already.

At first I stuck with enabling ADB in my kindle but I eventually figure out how to do that. However, now when I hook my kindle to pc, the adb still doesn't work as a result adb.exe (command: adb devices) can not recognize my kindle device. At same time when my kindle connects to pc I found kindle is recognized as a removable device (MTP mode). And in kindle, in notification bar there are 2 items, one tells me that kindle is connect as Media Device and the other tells me ADB is enable. This is weird when both MTP and ADB are enabled at same time and I guess maybe this is the reason why pc can not see kindle in adb mode.

Then I tried to disable MTP (uncheck MTP in setting-storage-setting) to see whether ADB will work, I found I just can not do it, I can only switch between MTP and PTP rather than unselect both MTP and PTP.

Fastboot always works.

Appreciate if any help.
[8.9" Kindle Fire HD Android Development] AlexAquarium:
While you are figuring out the problem, you can still backup this boot0 by issuing the command from the kindle cmd terminal and copy it over to some place safe.
[8.9" Kindle Fire HD Android Development] timnan:
Did it as you said.

Thanks.
[8.9" Kindle Fire HD Android Development] galearned:
CM10 cannot be detected with ADB devices

I am pretty sure the reason is that the Vendor ID in the Cm10 build is not 0x1949 (Kindle).

Before you flashed the Cm10. the Vendor ID was 0x1949 and after was not (Probably was google 0x18D1).

Unless your PC is setup to recognize the new Vendor ID, ADB and Fastboot will no longer work.

The good news is that if you loaded 2nd bootloader and TWRP, if you are in recovery, the recovery Vendor ID is 0x1949.

The solution is to wait until Hashcode modifies his CM10 builds to put the 0x1949 vendor ID back into the build.

This kind of thing happens more often than you would think and creates some issues after a ROM change.

Regards Jerry
[8.9" Kindle Fire HD Android Development] soupmagnet:
[MENTION=4243514]Hashcode[/MENTION]

Just curious...is this something that was added to Amazon's code (intentionally, perhaps?), or is it just an unfortunate byproduct of making a mistake while attempting to modify the device?

Is it due to a recent update or had it always been the case?
[8.9" Kindle Fire HD Android Development] Hashcode:
There is code in 1 of the bootloaders to erase the boot0 block and reset the info after many failed boots. And this info is so important that I felt it was worth keeping a backup of. Without it, you can never re-register the Kindle w/ Amazon services.
[8.9" Kindle Fire HD Android Development] soupmagnet:
So, apart from screwing people over, would there be any real need for such an addition?