yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] techdigital:
As long as you can get to the bootloader all isnt lost, you could use odin from there to reflash the images with the toolkit

---------- Post added at 11:20 AM ---------- Previous post was at 11:17 AM ----------

Also if I remember correctly you should be able to get adb in recovery,if you can get the files and push them to the device wouldnt that work?
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] techdigital:
http://xdaforums.com/showthread.php?t=2341488

---------- Post added at 12:35 PM ---------- Previous post was at 12:31 PM ----------

What happens if you press vol- plus power? do you get the warning message? can you get into that mode?
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] Scorpion_Ibm:
Read this http://xdaforums.com/showthread.php?t=2329139 and its comments where i helped a user with something close to what u have

Also when in recovery try adb reboot download ... And see if it reboots in download mode that would help alot
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jonnierod:
The question is can I get a digitally signed copy to flash?
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jonnierod:
It just goes straight into recovery mode, no matter what I do. Never goes into or gives me the option to go into download mode.

I can get into adb and flash things that way, but if what I'm trying to flash isn't digitally signed it won't flash it because I lost root.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] techdigital:
There has to be some sort of exploit to flash it anyway, or we wouldnt have root in the first place

---------- Post added at 02:21 PM ---------- Previous post was at 02:20 PM ----------

There may be a way to use the toolkit to boot temporary twrp recovery
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jonnierod:
If there's a way to do it through adb I'm all ears. The only method I'm familiar with is through Odin, which I can't use right now.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] techdigital:
Idea

I think i have a answer, since youre stuck in recovery and it does register in adb right? download the toolkit here

http://xdaforums.com/showthread.php?t=2341488

follow all instructions in the command prompt, choose your model and version of last installed software, if not listed choose 4.1.2

then choose option 3 to install a recovery image, i will reflash my device and make a recovery zip for you to flash in twrp and that should fix it or so i think.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] kcrudup:
Wait- why can't you get into Download Mode? (You've tried holding down "Power" and "Volume Down", I'm assuming?) Plus, you've mentioned "signed images"- which model do you have? (neither the N8000 nor N8013 require signed images, as they're factory unlocked).
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] techdigital:
Just so you know Volume Down is the one closest to the power button!!! and if you can get into download mode you could also flash a recovery from there and then install a rom.

http://rootgalaxynote.com/galaxy-no...t-galaxy-note-10-1-easiest-methodcwmmethod-2/
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jonnierod:
No, it just goes straight into recovery mode. No warning, no option to go into download mode.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jonnierod:
I'm not sure exactly. Since something went wrong when I flashed my ROM I also lost my backup of the original Samsung ROM that came with the tablet. Not sure if that's a related problem or not. Due to not having a backup I downloaded a stock ROM from SamMobile and flashed that one. That's when I lost my ability to get into download mode and the CWM I was using.

It is a N8013. There is one wire leading from the battery labeled N8000, which caused some confusion to me, but it is a WiFi tablet, not 3G, and all other documentation says it's a N8013. Maybe Samsung uses similar internal parts.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] kcrudup:
Oh, you mean that screen that says "Your tablet must be reset via Kies" or the like? That's actually download mode- you'll get that mode if for whatever reason your previous flash didn't work. You'll need to get either Odin or Heimdall at this point though.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jonnierod:
Yes, I've gotten quiet proficient at the various modes over the last few days trying to fix this, lol.

I've tried it both ways just to be sure, neither gets me into download mode, regrettably. I've never seen anything like it. I'm assuming this has something to do with the ROM I flashed from SamMobile.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jonnierod:
I also have a friend who is more proficient with these things than I am working on it, the tablet is actually at his house right now. In regards to the toolkit he wrote this:

http://xdaforums.com/showthread.php?t=2341488

Failed to send

i had tried that out anyways just to humor the troubleshooting gods

Failed to send

it doesnt do **** if you dont have download mode

Failed to send

the closest we can get to communicating with it is through adb., If they can fdigure out a way to flash a stock recovery via unrooted adb shell then im all ears.

He's also trying to figure out if there is a way to side load a ROM.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] techdigital:
It shouldnt matter if its in recovery mode with the toolkit as long as your computer can connect adb

You load a insecure boot image of twrp and flash the rom
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jonnierod:
Update:

We were able to get into download mode and run the toolkit. We flashed a stock ROM but that did not recreate /efs as we had hoped.

We are now attempting to rebuild /efs manually.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jonnierod:
SUCCESS!

We've successfully fixed /efs and restored the ROM. Now trying to get it out of factory mode.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] techdigital:
Congrats! I knew the toolkit was the way to go!

---------- Post added at 11:37 PM ---------- Previous post was at 11:33 PM ----------

That's why I said use the toolkit to get recovery, then I would apply a fresh flash to my tab then make a backup of everything including efs and send it to you to flash
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jonnierod:
Yup, that's what we finally were able to do. Tablet is running like a champ now. Thanks for all the help everyone, much appreciated.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] Scorpion_Ibm:
How did you fix efs manually? :silly:
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jonnierod:
There's a link for it earlier in the thread, or there's a thread somewhere on XDA for it.
[LG Optimus L9 P760, P765, P768, P769] shevin:
I have t-mobile LG P769 L9 , I have rooted it,

it keeps asking prompting me to update from v20f to v20h and it downloads and restarts and it shows the android icon for repairing/update

then it boots normally, then after a few days it asks me again to update from v20f to v20h again.

whats the problem ? how can I stop it, or update it once forever?
[LG Optimus L9 P760, P765, P768, P769] boo_radley:
Sorry I don't know who to credit the info too but I've stopped update notifs using android tuner under apps long press google.services.framework. select permissions then services. Uncheck system.updatesystemservice.
[LG Optimus L9 P760, P765, P768, P769] BrianRosenthal:
Do you mean Android Tuner by "3c"? I can't figure out how to follow your instructions on this app.

-Brian
[LG Optimus L9 P760, P765, P768, P769] boo_radley:
Yes in android tuner. Under apps section. Long press google.framework.services. option tab pops up. Select permissions. Then from there select services then uncheck

update.systemupdateservice

Tell me where your having trouble. You basically have to search for google.services framework which you can find in android tuners app manager. Long press for options.
[LG Optimus L9 P760, P765, P768, P769] shevin:
is there any way that I could update to the latest version for real ? I would like to have latest version !
[LG Optimus L9 P760, P765, P768, P769] boo_radley:
Offline flash method it's a thread by cmahendra. ..and version 20h is newest for t-mob. Not sure what you have. There also might be easier way if any one knows. Such as syncing phone with computer to lg and update latest firmware (software)(kdz) whatever I should call it.
[LG Optimus L9 P760, P765, P768, P769] shevin:
could someone please give me easy way to upgrade from v20f to v20h t-mobile usa ?
[LG Optimus L9 P760, P765, P768, P769] aod990:
- Official LG Mobile Support Tool

- Offline KDZ Flash
[LG Optimus L9 P760, P765, P768, P769] wolf howl:
Thanks for that! That annoying little reminder was always coming up and it wouldn't allow me to update without failing so I'm excited to not see it remind me again! Thanks!
[AT&T Galaxy Note 3 General] tyiphius:
I listen to a lot to a lot of music on youtube. Its great that I can use the pen windows to have multiple apps open at the same time, but when I minimize the youtube app it stops playing. You can drag the window as far as you can into one of bottom corners but It becomes annoying when you need to use the keyboard and need to reposition it.

I did a little research and came upon this thread http://xdaforums.com/showthread.php?t=1529715

Its an older version of the youtube app but its been modded and it works when its minimized via pen window.

Follow the instructions in the linked thread and make sure "Screen off playback" is enabled.

If you are rooted and dont want to use the modded youtube, you could always download an app like "Youtube keep alive" or similar and use it via pen window, provided you have "Pen Window Manager" installed (http://xdaforums.com/showthread.php?t=2467944)
[Galaxy S 4 Q&A, Help & Troubleshooting] Mr2HitKO:
I have a Galaxy s4. When I plug it in to the wall charger, it says, changing paused, temperature too low. I have an app to read my phone temperature and it says give or take -5 c. I've tried a master reset and tried looking online for solutions, I also tried putting my battery in another s4 and it works fine, the only way I can charge my phone is to use a heating app for about an hour Do you have any suggestions on how to fix this glitch? i tried calibrating my heat censor but i don't think it worked, the heat sensor in my phone doesn't seem to work. Any help you can give me is greatly appreciated. maybe if i could get an app to force charge my phone, or disable my heat sensor all together? i tried finding a diagram of the mother board so i know exactly were the heat sensor is and i also had no luck. PLEASE HELP!!!
[JAM, MDA Compact, S100 Software Upgrading] richardzen:
hi does anyone know if you can use s100 hands free ?

is there any software available for this ?

Thanks :D
[JAM, MDA Compact, S100 Software Upgrading] Facemodder:
just press and hold the green button for a few sec and you are calling hands-free :)
[One (M7) Q&A, Help & Troubleshooting] broli-zn:
Ok so i have searched but unable to find an answer to my question.

I want to downgrade my Hboot from 1.54 back to 1.44. I do have s-off. I s-offed when my hboot was on 1.44 using revone. My hboot was upgraded after doing a firmware update.

So i need to send my phone in for repairs (the infamous purple camera) and i want to downgrade so I can return to stock, remove "tampered" and relock.

As stated I am currently S-off and have read its possible to downgrade if you are s-off, just need to be pointed in the right direction
[One (M7) Q&A, Help & Troubleshooting] godutch:
I wouldn't downgrade and s-on for warranty, it isn't necessary, they won't check and you will regret it because you will get back your phone s-on and upgraded to hboot 1.54, so non-s-offable for now. I did it too without any problems.

Just make you phone stock again (install a stock ruu is it is available), lock (not relock) your phone and remove tampered flag (running an ruu would remove it, if there is no ruu do it first because revone won't work without root on hboot 1.54)

BTW purple camera is just software whitebalance problem not a hardware problem
[One (M7) Q&A, Help & Troubleshooting] CoryTallman:
You just need to downgradethe firmware. It contains the hboot.

But as [MENTION=1865045]godutch[/MENTION] said, it's not necessary.
[One (M7) Q&A, Help & Troubleshooting] broli-zn:
Ok cool, thanks guys, so I just need a flash a firmware zip containing 1.44 Hboot and im good to go?

Basically i just want to get rid of the tampered flag.

Iv done the 4.3 upgrades with supposedly fix the camera but its made no effect on mine :crying: so the only other option I have to try and get them to change the camera module.

Thanks again guys. Much appreciated. You will get a thanks each
[One (M7) Q&A, Help & Troubleshooting] criszz:
you don't need to downgrade. h-boot 1.54 is normal and considerated STOCK for devices who made OTA update.

don't do stupid thing's

i removed tampared flag with revone -t
[One (M7) Q&A, Help & Troubleshooting] broli-zn:
i flashed firmware using ADB, revone doesnt work with 1.54 unfortunately
[One (M7) Q&A, Help & Troubleshooting] godutch:
it does but you need to be s-off and rooted for it to work but you don't have to do what you are trying to do and you will regret it later....
[One (M7) Q&A, Help & Troubleshooting] criszz:
just try with 1.54 ;), multiple times
[One (M7) Q&A, Help & Troubleshooting] amauryaa:
hboot 1.55

I had my phone repaired twice and they didn't say any thing about the boot loader being unlock. However, since that I have s-off and the phone needs to go to repair for the microphone not working and I wonder if I could either s-on and lock the boot loader with hboot 1.55? If you have any advice, I would appreciate it. Thanks.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
not recommended, as far as i've seen, going from s-off to s-on (on 100% stock everything), after a few reboots, has a high chance of resulting in "tamper detected - rebooting" and the TAMPERED sign is back.
[Nexus 7 Q&A, Help & Troubleshooting] 37nook:
For updating to android 4.3 , I flashed my N7.

I download the package the factory image from Google .

I entered the fastboot and do things following:

fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-razor-jss15r.zip

when it come to

fastboot -w update image-razor-jss15r.zip

there is a warning about the bootloader

At this time ,bootloader seems didn't chaged , it's still grouper not flo.

I modified the android-info.txt to cheat the program and the tragedy start.

The windows remind me there is 6 unknown device. And then it fully bricked.

Now, When I turn on the N7, the screen stay blank.

APX device appear while connect to PC.

Can't enter fastboot mode ,can't enter recovery. even the screen can't be lighten.

Anyone else meet the same trouble or someone can help?

Before this, I have had try the follow tools.

The Nexus7 toolkit--won't work

tegra-android-developer-pack from nvidia website tegra developer tools --won't work

nvflash and wheelie from androidroot.mobi --can't work --(It's a rediculous project I think, If the fastboot work,why we need to flash rom via nvflash)
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
Sorry, but if you really flashed the files above, you have bricked your N7 completely. Probably you should have looked around and informed yourself before starting to flash files which are not compatible with the N7.

Btw. if you had used wheelie before, you would have some recovery files and you would be able to recover yourself from the brick. So it's not a ridiculous project at all.
[Nexus 7 Q&A, Help & Troubleshooting] Erovia:
I thought it's common sense to read, read, read and read a bit more faqs/how-tos/guides before doing anything to a device.

First of all, 'grouper' is the codename of the 1st gen N7 Wi-Fi (the 2012 model) while 'flo' is the 2nd gen N7 (2013 model), so you can't flash ones image to the other device.

Secondly, your device might be saved, but only if you still can access it with fastboot. If so, then flash the proper images for your device using a toolkit or a guide, if not, then you have a nice paperweight.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
This is a text book example of what happens when people don't read enough, and don't fully understand what they're doing. And it's not as if there aren't enough guides and how-to's here on XDA... and even on other forums!

Hi, 37nook...

You have almost certainly over-written your bootloader with a completely incompatible version designed for a different tablet (2nd gen Nexus 7)... and thus you are hardbricked. This is why you can't access fastboot mode and why your tablet defaults to APX mode when you hook it up to your PC.

And unless you had at some point run the

flatline

procedure BEFORE being bricked, your tablet is unrecoverable.

Regarding flatline (nvFlash) itself, it's designed, primarily as an emergency recovery measure... and not as a replacement for fastboot, as you seem to suggest in your post. It's preemptive and needs to have been executed before being 'bricked' in order to generate your own unique 'wheelie blobs', which are created on a per-device basis. Without these, nvFlash alone is useless.

It's not much comfort, I know... but I can only suggest you chalk this down to experience, and next time, with whatever tablet/phone you next end up with.... PAY ATTENTION TO WHAT YOUR DOING, AND READ EVERYTHING, and if you're still a little unsure... POST A QUESTION. Better to feel like you're asking a dumb question (which might not be so dumb), than end up with an expensive paperweight:(.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] 37nook:
nvflash is not a good choice for one to flash his device because of higher risk.

there is too many tools available with a lower risk.

That's the reason I didn't use wheelie before.

You are right, I am a very impatient person, and now I get a lesson.
[Nexus 7 Q&A, Help & Troubleshooting] 37nook:
It's actually a nice paperweight now.

Thank you for your reply which tells me where I went wrong.

It's a really serious mistake, and it's also a painful story.

I can't access it with fastboot ,so said.
[Nexus 7 Q&A, Help & Troubleshooting] 37nook:
Thank you for your suggestion

There is still a question

I actually run these code twice.

First time a got a warning. because of the file content of android-info.txt in image-razor-jss15r.zip

the code

fastboot reboot-bootloader

must have been executed, and the bootloader is still grouper.

means the code

fastboot flash bootloader bootloader-flo-flo-03.14_img

didn't work

And the second time

fastboot -w update image-razor-jss15r.zip

led to the tragedy because I modified the android-info_txt in image-razor-jss15r_zip

What happened in updating image-razor-jss15r_zip ?
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
That is indeed puzzling... if after flashing the incorrect bootloader, and the bootloader is still showing as 'grouper' AFTER fastboot reboot-bootloader, then I'm puzzled.

I'm also further puzzled, that the rest of the flash went ahead... seemingly successfully. I know on my 'grouper', when fastboot flashing back to factory stock... if the bootloader isn't the correct version (for that version of factory stock), the flash aborts with the message 'Incorrect bootloader version'. I'm not sufficiently knowledgable though, concerning the specific details of the second gen Nexus 7 and it's associated stock factory images, to make further comment.

It's just possible (though unlikely), you might just be stuck in APX mode, instead of having a corrupted bootloader.

I assume you've tried all the usual button press combos... detailed

here

.

If you can boot into the bootloader, your Nexus 7 is recoverable... though I'm not optimistic:(.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] zamboniman87:
OP, did you ever have any luck?
[Nexus 7 Q&A, Help & Troubleshooting] xateeq:
+1
[Nexus 7 Q&A, Help & Troubleshooting] funkyo0o:
Begining to think that it has to do with the nvflash.exe version is why.

After downloading another nvflash.exe with it's acompanying .dll's I found a nvflash program that executed and did not display the familiar "unknown device found" error message.I did it with the "NVidia USB Recovery mode for mobile" driver, nothing fancy.I was surprised that that nvflash version at least ran.The nvflash version i used is the nvflashtf201which is the Tegra3 ICS nvflash.I run that version of nvflash and I at least get this message in the command prompt on Windows XP sp3 after issuing a "harmless" nvflash --sync command.

Nvflash v1.13.87205 started

chip uid from BR is: 0x0000000000000000015d483bd137ec12

rcm version 0X4

Command send failed (usb write failed)

I googled around and some people say that it is because the bootloader is locked, and other say it is because the SBK version is 2 or higher or somthing if im not mistaken.As far as I know is that before I got the gadget hard bricked the boot loader was unlocked.I have even gone as far as to reformating my other computer and installing Unity Linux just to get my device accepting the nvflash commands I have configured the "rules.d" files to what "lsusb" shows I have tried different versions of nvflash like from upload sites and even from nvidias site even tried a newer cable (the newer cable works better but the old one still works)., I downloaded the "Cardhu" "Jelly Bean" stuff from the Tegra Android Development Pack 2.0r6 ( not 2.0r7 because the Tegra Android Development Pack 2.0r7 gives me an md5 hash blah blah error and would not install). The Tegra Android Development Pack 2.0r6 comes with nvflash.The reason I downloaded it was just to get nvflash.I do not have any blob files backed up, I only have the SBK from the chip uid of my device thus would like to try and get a hold of an nvflash in which the "--sbk" command parameter has not been deprecated.I understand that maybe i might not get lucky as the the newer nvflash programs might all have the "--sbk" parameter neutered as well as a few more command parameters.So does anyone know if there is a nvflash version that has the -"--sbk" command paramete support so that I can test and verify if the failed error message above if because I did not supply the program a Secure Boot Key or am I wrong about thinking I need to supply nvflash with a Secure Boot Key in this newer version given the program has a recent algorithm given the program found my devices chip uid as shown in the comman line output above? If thers nothing I can do then can some one comfirm.If there is another nvflash binary that is Tegra3 ICS and has the "--sbk" parameter then point me to where I can find it, or pm me. Thanks