yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] spthacker:
Worked like a treat thanks very much :)

Sent from my Nexus 7
[Nexus 7 Android Development] mondokat:
I just flashed the new bootloader. Works great, no bootloops or anything. I can still get into my cm10 nightly and i can get to recovery without a usb cable now. Great!
[Nexus 7 Android Development] osm0sis:
Anybody have any issues with the new bootloader? I've been trying to fastboot flash system and it's been stuck at "sending" for like half an hour.

I updated my Galaxy Nexus yesterday via fastboot the same way but it definitely didn't take this long..

Edit: NM. Must have been some random derp in the Naked Android Driver. Rebooted and it worked great. 90 seconds to send and write. :good:
[Nexus 7 Android Development] gunz.jones:
Most of the roms don't have 3.41 boot loader install included. Check your screen to see if it did. I just flashed this as normal because I am waiting for 4.1.2 with binaries to be updated into more ROMs before going on another flashing spree.
[Nexus 7 Android Development] bucketachicken:
Yes, yes I can. From bootloader. Power off the N7, vol down plus power, tablet boots into bootloader, press volume down twice to choose "Recovery mode" and press power to choose, tablet reboots right into CWR. All by the book, all while disconnected from any computer. Can video it if you need proof, lol.

Edit: just struck me you may have been referring to the Tab 10.1. In that case, no. Without a pc, it will do literally nothing. With a usb connection to my laptop, I can't get recovery, bootloader, download, adb, fastboot, or a regular boot up. The only thing I can do is use Nvflash to get it into "Nvflash Recovery Mode" at which point no other command I have found from any amount of googling will do anything whatsoever. It's a retail 32 GB Wifi only Tab 10.1, had an unlocked bootloader at purchase (unlock symbol on boot up, before this mess at least, lol), like many others also had. Probably one of the first run models, given that I bought it a week or so after they were released (and thus why it's out of warranty already). The thing is truly nothing but a paperweight atm, it's killing me!
[Nexus 7 Android Development] Pithism:
So I flashed the cm 10 and tried flashing goo version with newest twrp and I'm still stuck at boot loop. Any idea next. Should I try pushing it via fastboot.

I also can't turn it off. It keeps rebooting
[Nexus 7 Android Development] GreenXSniper:
you have to flash the 3.34 bootloader
[Nexus 7 Android Development] Pithism:
aww lame sauce. I thought cm 10 nightly 10/11/12 would have worked because its 4.1.2. im guessing the binaries arent updated?

But thanks.

Any idea on how to turn it off?
[Nexus 7 Android Development] dude_uuk:
Sorry for being a noob, but jus want to know what is the beeefit of flashing this bootloader?i am already in 4.1.2 flashed manually.thanks.
[Nexus 7 Android Development] rufh_s:
There's a bug in old bootloader 3.34 i.e you can't get into recovery/fastboot without PC but this new bootloader 3.41 solves the issue.. hope it clears :)
[Nexus 7 Android Development] poondog:
Sorry if this has been said before, but I flashed the new bootloader from the link in the OP via TWRP

Rebooted to recovery and its showing 3.34

Am I right in assuming it didn't work? Thanks :)
[Nexus 7 Android Development] Rycon33:
It could be due to twrp. I flashed the op's file a couple of days ago on cwm without any problem. I'm on cm10 btw.

Or you may also just try fastbooting the new bootloader image file, extract it from the factory image provided by Google.

Tapatalked from my Ace 2
[Nexus 7 Android Development] vladthedog:
I'm running twrp and it flashed just fine.

biggest thing i recommend is everyone check your md5 hash
[Nexus 7 Android Development] poondog:
Thanks for the help guys :)

I read a few pages back to flash, then reboot into android, then reboot back to bootloader and it will be updated.

So I did that and it worked. I used TWRP to flash it.

Also, I just accessed recovery from the bootloader without PC connection so the bug must be gone :D
[Nexus 7 Android Development] Pithism:
This is getting ridiclious. I pushed it through fastboot with a img file and it still gets stuck. I dont know what else to do. anyone have any ideas.
[Nexus 7 Android Development] M3drvr:
Sat back with my rum, downloaded IMG file, pushed it with fastboot, erased my recovery, pushed new twrp IMG recovery with fastboot, rebooted bootloader, and had another rum, used bootloader to boot into the recovery and no problems. Everything works perfectly now. Finally a fully functional bootloader!
[Nexus 7 Android Development] syzkk:
yes exactly like me and many others, the reason why some have no problem while many others have still unknown...

only thing you can do is revert to old bootloader 3.34, or if you want to try wipe all the storage to have factory image.

if someone know the real problem or related thread for solution please let me know...
[Nexus 7 Android Development] LKNim:
Is there any way to flash bootloader when it's locked and I can't get into recovery since I flashed the 3.41 bootloader with fastboot mode.

Flashed the 4.1.2 ROM rooted and fail to flash another ROM and I re-locked my bootloader lol
[Nexus 7 Android Development] cyanogendroid:
HELP GUYS!!! I flashed this on top of PA 2.7 because the OP said it could be flashed on top of anything and it after that it rebooted to the google screen and will only go to the bootloader. I have tried flashing a stock image with the nexus root tool kit and yes its adb identified, but it tells me thet the flash was rejected! I am unable to flash recovery or anything through fastboot!

EDIT: I fixed it! Phew! that was scary... so what I had to end up doing is flashing the 4.1.1 image, not the 4.1.2 one from google. Just a heads up to you guys.
[Nexus 7 Android Development] testulous:
Worked for me, verified with untethered boot into boot loader!

I flashed pa 2.2 then hit the goo.im link, it opened in goo manager and downloaded. Flashed, success.
[Nexus 7 Android Development] blitzkriegh:
Can someone share the 3.34 boot image pls bec its no longer available at the Google dev site. Thanks
[Nexus 7 Android Development] jayyo:
Here's the naksi-jro03d-factory-e102ba72.tgz: http://dl.dropbox.com/u/7376317/nakasi-jro03d-factory-e102ba72.tgz

md5: 7F79D40F03BAB0F9B2871EAAE74AC61E

sha1: E102BA729BF34AEE5B2A8AE5F309854E6CDB3964

boot.img is inside it. It's from the google developer site last week.
[Nexus 7 Android Development] blitzkriegh:
Thanks! Managed to downgrade to 3.34 boot loader but after rebooting to recovery, nothing happens, was just at Google screen'...
[Nexus 7 Android Development] swieder711:
I have joined the club of people that cant get the N7 into recovery. I have 3.41 bootloader installed along with CWM 6.0.1 touch. On top of that I have 4.1.2 ROM (JZo54K) which is running nicely with the Franco kernel.

I have tried different USB cables, different custom recoveries, different computers. In all cases I CANNOT get into recovery mode either thru ADB, bootloader, or WUG/N7 toolkit.

I am about ready to downgrade the bootloader back to 3.34 to see if that provides any help.

EDIT: I downgraded the bootloader to 3.34 and for the first time in 24 hours I can reboot into CWM mode with or without a USB cable!

EDIT2: Just completed my first Nandroid through the CWM recovery app and custom recovery utility. I should sleep better tonight and hopefully get to bed earlier too!
[Nexus 7 Android Development] jayyo:
Did you fastboot flash a custom recovery, then reboot bootloader in fastboot?
[Nexus 7 Android Development] lilphil240:
I was able to flash touch-less CWM through rommanager. Was able to get back into recovery.
[Nexus 7 Android Development] diomark:
Does anyone have the link for the old bootloader?
[Nexus 7 Android Development] jayyo:
It's inside this: http://dl.dropbox.com/u/7376317/nakasi-jro03d-factory-e102ba72.tgz. This is the factory image from Google dev site (before they released the 4.1.2 image).

I had to use 3.34 bootloader to get recovery to stick and re-root. I then flashed 3.41 bootloader.

This is from Faux123's kernel thread. Faux123 said:

edit: should have included this:

md5: 7F79D40F03BAB0F9B2871EAAE74AC61E

sha1: E102BA729BF34AEE5B2A8AE5F309854E6CDB3964
[Nexus 7 Android Development] diomark:
I was able to downgrade to the 3.34 boot loader, and reboot into recovery/install root.. But after loading the new bootloader (3.41), I'm again unable to reach recovery..

At least I have root now.. but... what's up w/ going into recovery??
[Nexus 7 Android Development] smirkis:
don't leave your device connected via USB when trying to access recovery...

all u people having issues make me laugh. seriously.

and for the record, if u flashed a bad bootloader or corrupt downloaded bootloader, your device won't even boot. this zip does not check for md5 before replacing it so of course u should check md5 before flashing. all u people having issues, your issues are else where (user error).
[Nexus 7 Android Development] blitzkriegh:
At my 1st try I didn't flashed a custom recovery because I was expecting the stock recovery would be present after loading the stock factory image of J300RD...

After flashing, did the rooting process and flashed the 3.41 but still no recovery either via boot loader, fast boot using the nexus toolkit.

I tried to repeat the process of flashing the factory image with 3.34 boot loader, rooted and this time I flashed the image recovery of twrp. After doing this process, I can boot to recovery now. Did a nandroid backup and flashed the 4.1.2 hyperglayperglazed ROM.

Having said this, do I still need the flash the boot loader 3.41 separately?
[Nexus 7 Android Development] jayyo:
I'd say yes, so the bootloader matches the kernel. Use this recovery to be safe: http://xdaforums.com/attachment.php?attachmentid=1402628&d=1350260065
[Nexus 7 Android Development] deltantor:
You are saying it is user error when there is something wrong for a lot of people.

I wiped data, installed PA 2.2, and then flashed this bootloader and could not boot into recovery, so then I tried erasing recovering and flashing cwm, could not get into recovery, erased recovery, tried twrp, could not get into recovery. device booted into rom just fine, but could not get into recovery either from reboot recovery or trying to cold boot into it. So I flashed 3.34 bootloader again and suddenly could get into recovery just fine. Tried 3.41 bootloader again, still not getting into recovery. Wiped device, flashed the 4.1.2 factory image, including bootloader, couldnt get into recovery. Tried oem unlocking and then flashing twrp or cwm, still not getting into recovery, plugged into usb or no.

This is not just user error.
[Nexus 7 Android Development] irminsul:
I'm also unable to get to recovery when on 3.41 bootloader, either via fastboot, adb, bootloader. Reverting to 3.34 fixes the issue, but it's very strange. It seems there's no fix at all, maybe it has to do with hardware revisions. I'm having an 8GB UK model. What variants are other '3.41 bug' people having?
[Nexus 7 Android Development] ricardowec:
If you have one of the first N7s, they just dot take 3.41.

If you downgraded to 3.34 flash TWRP. 2.2.2 using the tool. You should not be able to get into recovery from the bootloader ever.

I have two N7s. One is July pre order variant 1 that does not take 3.41. The other is a September batch variant 3 cpu that works just fine.

Sent using The Beast via Tapatalk 2
[Nexus 7 Android Development] comminus:
Interesting. Are both tablets ER3 hardware?
[Nexus 7 Android Development] ricardowec:
I am not sure. I don't have the boxes with me right now.

The only thing I can assure you they are different as i can tell from the kernel info.

I have to clarify something. Variant 1 cpu you can flash 3. 41 but it just does not work, not even flashing after 4.1 2. It will hung on the Google logo or boot loop.

Those early N7s are a problem. Unfortunately I didn't realize until I got the second one.... Too late.

The September one works like a charm. The July one has the speaker blown. I bought both in the Play Store and tried to rma the first one without success.

Sent using The Beast via Tapatalk 2
[Nexus 7 Android Development] mcarnevali:
I was using JB 4.1.2 with bootloader 3.34, I flashed this bootloader but didn't work for me, I installed 3.34 again and everything is working fine.

Using the bootloader 3.41, I cannot get into recovery with or without usb cable.
[Nexus 7 Android Development] spaceman860:
People that can't get into recovery from bootloader v3.41try this CWM_JZO54K_grouper_bootloader_v3.41.zip

http://db.tt/SQlpz2vc their is a zip file floating around that does not work

Sent from my BAKED N7
[Nexus 7 Android Development] smirkis:
I still say user error.

I have a preorder n7 and flashed he new bootloader without issues.

and I have one from a few weeks ago, flashed fine and works fine.

stop using root kits. open up a cmd prompt and adb reboot bootloader, fastboot flash bootloader...

the bootloader works fine, and so does 90% of the people who flashed it. the difference is, no one posts when it works, just all of you who have issues post back lol.

they would not push this update to the world if it didn't work on all n7 models, otherwise they would ota brick all preorders which I'm sure they would never do....
[Nexus 7 Android Development] hhwong:
I have the same issue mcarnevali.

Also spaceman860, your file doesnt work, its the same as the original 3.41 bootloader. It shows the google icon, and just reboot, show google icon again, and boot normally into rom.

I guess i am stuck with 3.34 until the next bootloader comes out. :(
[Nexus 7 Android Development] spaceman860:
If you extract the bootloader from Google images and use fastboot to flash it you should not have any issues

Sent from my BAKED Nexus
[Nexus 7 Android Development] mcarnevali:
Me too... :(
[Nexus 7 Android Development] deltantor:
Never used a root kit on this, everything was done in adb and fastboot. And have been doing this with the boot loader from the 4.1.2 factory image.
[Nexus 7 Android Development] hhwong:
I did that too, doesnt work.

image was directly extracted from 4.1.2 image file directly from google......

Same issue, everything works except i cant get in recovery.
[Nexus 7 Android Development] zAo_:
Ok, nailed it:

Download this file and unzip.

Connect your Nexus 7;

Enable USB Debugging;

Verify that the Nexus is connected correctly

adb devices

Reboot into bootloader

adb reboot-bootloader

Flash bootloader

fastboot flash bootloader bootloader-grouper-3.34.img

Reboot new bootloader:

adb reboot-bootloader

Flash CWM:

fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img

Boot CWM:

fastboot boot recovery-clockwork-touch-6.0.1.0-grouper.img

Make new CWM perminent:

adb shell mount /system
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell umount /system

Push SuperSU

adb push CWM-SuperSU-v0.96.zip /sdcard/Download

Flash SuperSu normally.

Reboot!
[Nexus 7 Android Development] syzkk:
Sorry what is the purpose of this, to be back to old bootloader?
[Nexus 7 Android Development] gunz.jones:
It appears so. He lists the old IMG. Must be he is one of few the new one didn't work for.
[Nexus 7 Android Development] zAo_:
Sorry, but it's a workaround for the unhappy few who can't reboot in recovery after 4.1.2. This will get you 1) the old bootloader, 2) latest CWM and 3) Root without reflashing Android itself.
[Nexus 7 Android Development] djd338:
This zip worked 1st time for me & my pre-ordered 16gb unit. Flashed with TWRP 2.3.1.0. I flashed EOS build 34 first to make sure I had a compatible kernel. Then the bootloader zip. I read somewhere to boot to android immediately after flashing, then boot to bootloader. When I did, I had the new bootloader. Worked for me.
[Nexus 7 Android Development] Anon9mouz:
It flashes but does nothing I guess I'll take the long route or short either or and ota update and re-root and recovery

__________________________________________________
[Nexus 7 Android Development] phonic:
I ran into the exact same problem.

First gen N7, running fine with old firmware. Upgraded to new 4.1.2 firmware and bootloader. No longer able to get into recovery. After a couple hours of trial and error, including a full reflash of 4.1.2 stock, the only solution was to downgrade the bootloader to 3.34.

This is not a "user error" issue, but a problem with either the bootloader itself, or an incompatibility between it and a minority of devices.
[Nexus 7 Android Development] gunz.jones:
I would gather it's a common Asus hw issue at play. Happened with 101 and 201 devices on the ICS update bricking. It may not be letting the newer bootloader write to ROM correctly or something like that.
[Nexus 7 Android Development] Sultan.Alkhuzaie:
do i have to do all these steps like make new CWM peminent and flash the super su .zip
[Nexus 7 Android Development] phonic:
Those steps are more a complete "what to do if you don't have root, lost recovery and need to revert to the old bootloader". If one of those doesn't apply to you, you don't need to do that step.

My initial upgrade went fine, outside of losing access to recovery. I still had root and was able to reflash CWM. However, I wasn't able to access it, so tried various steps in troubleshooting including reflashing stock firmware (and thus losing root). So in my case, I had to reflash bootloader 3.34, CWM and SU. Your situation might be different, but it doesn't really hurt to do all the steps either.
[Nexus 7 Android Development] hhwong:
I dont get it, lol. I can simply flash the old bootloader back in just 1 step, why did you list a whole procedure to do all that? I am a little confused.

Maybe I am missing something?

Right now, I flashed the old bootloader back, i flashed the new TWRP too in the recovery partition, everything is back to normal except i need to hook usb up before going into recovery.

I tried 3.41 too in this setup, no luck still. I am guessing it is a hardware issue at this point, probably my patch of the tablet just dont accept this version. I hope google come up with a fix soon......sigh.......
[Nexus 7 Android Development] phonic:
FYI - Regardless of which bootloader works for you, you do NOT need to hook up your tablet to your computer to get into recovery mode. You can do it directly from the tablet by opening up a terminal emulator, running su, and then typing "reboot recovery". It takes about 20 seconds. This always worked even on 3.34.
[Nexus 7 Android Development] hhwong:
ahh good to know, is there a way to creat like a widget or some quick link with the command lines? I just tried it and it seems to be working with 3.34, gonna flash 3.41 and see if it works.
[Nexus 7 Android Development] phonic:
I'm not sure offhand, but I imagine someone makes an app that allows you to create a shortcut command and turn it into a widget. Keep in mind that it would need root permissions to reboot into recovery.

Also, while this method works to reboot the N7 into recovery mode regardless of firmware/bootloader/etc., if the 3.41 bootloader is having issues getting into recovery mode on your device (which is the case with mine as well as others), it won't work. In my case it reboots, attempts to go into recovery mode, but then just boots into android normally. But assuming you can get into recovery on 3.41, the 'reboot recovery' command will work just fine.
[Nexus 7 Android Development] syzkk:
there are so many reboot apps that can let you boot to recovery, even rom manager or goo.im can do that. it has nothing to do with 3.41.

this is off the topic.
[Nexus 7 Android Development] hhwong:
yeah i just tried it, 3.41 just wont get into recovery no matter what, rolled back to 3.34, ahh well.......
[Nexus 7 Android Development] phonic:
What version of the N7 do you have? Was it part of the first batch that went out (C6 or whatever)? Mine is and has the problem. I know many people on XDA who got first batch N7s returned them for defects, so I'm wondering if there is a HW difference in the later models that the prior ones don't have, resulting in this 'glitch' for the latter.
[Nexus 7 Android Development] brizey:
My 60 worked just fine.
[Samsung Epic 4G Touch] erasable:
So I switched from Sprint to vzw a few months ago. I still haven't paid off sprint so my e4gt has a bad ESN. Sprint just send me a letter with a padded envelope offering me $100 to recycle my phone. Worth it or no?
[Samsung Epic 4G Touch] garwynn:
If it will go against the bill, why not?
[Samsung Epic 4G Touch] tdunham:
And if he owes them money, good luck getting that check. :rolleyes:
[Samsung Epic 4G Touch] Unknown Zone:
100 is about right if it is in good condition, ebay is also about 100+/- for a bad esn phone, I bought a et2 for a spare boost phone for 125
[Samsung Epic 4G Touch] garwynn:
True, but then it's $100 less on that bill.
[Samsung Epic 4G Touch] erasable:
I might try it out. It would save the headache of selling it on eBay.
[Samsung Epic 4G Touch] garwynn:
If you're not looking to make $$ on it you could also see if a dev needs it. Just an idea.
[Samsung Epic 4G Touch] erasable:
I have two of them laying around. I may sell the one and donate the other. I'm hurting for cash tho, so I have to think about it. But I would like to do something for the xda community at some point.
[Samsung Epic 4G Touch] RayTrue04:
Wait a couple months and then activate it. I did that with a phone given to my aunt. It wouldn't work when I first tried then a couple months later I tried again and it worked and got activated. I guess after a certain period the esn gets cleared out the system. Hmm maybe when the account is sent to the credit collectors the phone gets cleared out.
[Samsung Epic 4G Touch] GiantJay:
There is also swappa.com.
[Samsung Epic 4G Touch] erasable:
Thanks for the advice. I just checked them on an ESN checking site and they are clean. I agree with the debt collectors theory.

This kind of changes things. Sprint definitely isn't getting them. Not sure what my next move will be. Probably sell them.
[Samsung Epic 4G Touch] RayTrue04:
No problem glad I could help. I was surprised at that finding. Now when someone hands me a phone they have a debt on I wait it out 2-3 months and try. No issues as of yet =)
[Samsung Epic 4G Touch] fryingpan0613:
There is a guy making a sense themed ROM who had to get rid of his phone, i believe he would be worthy....

http://xdaforums.com/showthread.php?t=1894022
[Samsung Epic 4G Touch] Mattix724:
+1 for this idea. He had to sell his E4GT to pay for his daughter to go see a doctor.

He's still working in the theme but doesn't have a device to test it on.
[Samsung Epic 4G Touch] evol4g:
It may have a clean ESN but if you sold it the person couldn't activate it until the bill has been paid to clear the phone from the account.. I had to learn that the hard way when I sold a phone a while back
[Samsung Epic 4G Touch] Bannjio:
Should be cleared once has gone to collections though, yeah?
[Samsung Epic 4G Touch] evol4g:
Mine wasn't.. I had sold my phone some time after collections.. unless somethings changed
[Samsung Epic 4G Touch] RayTrue04:
Oh trust me it clears. I've already done it with a Samsung Transform, and OG Epic. Both had a previous balance. Took about 2-3 months before I was able to do an esn swap without rejection but it went through eventually.
[Samsung Epic 4G Touch] evol4g:
Mine was with Verizon so maybe they're different
[Samsung Epic 4G Touch] -EViL-KoNCEPTz-:
Verizon hardly ever clears esn's. I lost a blackberry I had on vzw and swapped to a flip phone, found the blackberry and they still wouldn't clear the esn, even tho I was the original owner and it was only swapped, I never even officially reported it lost/stolen. I had just called and said I needed to swap phones cuz id misplaced the active one, never filed a claim or anything. That stupid blackberry is still blacklisted and that was like 5 yyears ago

We are legion, for we are many.

Sent from the DarkSide of the GalaXy with a MEK device
[Samsung Epic 4G Touch] RayTrue04:
They made sure you never make a profit from it. You know they greedy like that lol