FORUMS

PSA: You Can Optimize Your Note 4’s Recents Menu & RAM

The Note 4 never had the fastest Recents Menu, and despite its 3GB of RAM, … more

XDA Picks: Best Apps of the Week (July 25 – Aug 1)

Apps are at the front and center of any smartphone experience, and with over a … more

Voices Of XDA: Orbiting The Earth With Android

Editor’s note: This week’s feature has been written by forum … more

CloudPlayer: DIY HiFi Music Streaming Solution

In our Helpful Guide to Music Streaming Services, we mentioned several different services … more

[Q] May have bricked my N7 (deb)

6 posts
Thanks Meter: 0
 
By jahames, Junior Member on 13th February 2014, 08:15 AM
Post Reply Subscribe to Thread Email Thread
So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.

Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024

I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.

I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
 
 
13th February 2014, 09:36 AM |#2  
StuMcBill's Avatar
Senior Member
Thanks Meter: 114
 
More
Quote:
Originally Posted by jahames

So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.

Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024

I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.

I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated

Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?

On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img

Hope this helps?

Stewart
13th February 2014, 09:44 AM |#3  
OP Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by StuMcBill

Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?

On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img

Hope this helps?

Stewart

Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
13th February 2014, 09:59 AM |#4  
StuMcBill's Avatar
Senior Member
Thanks Meter: 114
 
More
Quote:
Originally Posted by jahames

Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader

Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?

Maybe try flashing an older bootloader version?
13th February 2014, 10:43 AM |#5  
OP Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by StuMcBill

Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?

Maybe try flashing an older bootloader version?

Was working with the 4.4.2 image. Going to give the 4.4 a shot now
13th February 2014, 06:20 PM |#6  
OP Junior Member
Thanks Meter: 0
 
More
Same thing with 4.4...still stuck with the flo bootloader
13th February 2014, 06:38 PM |#7  
OP Junior Member
Thanks Meter: 0
 
More
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
13th February 2014, 07:21 PM |#8  
meekrawb's Avatar
Senior Member
Flag Katy, TX
Thanks Meter: 996
 
More
Quote:
Originally Posted by jahames

Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?

You flashed a recovery for flo. Flash one for deb.

Edit:
http://techerrata.com/browse/twrp2/deb
The Following User Says Thank You to meekrawb For This Useful Post: [ View ]
13th February 2014, 07:46 PM |#9  
OP Junior Member
Thanks Meter: 0
 
More
Reasonably sure I had a deb recovery, but apparently redownloading and reflashing the CWM image did the trick. Thanks!
14th February 2014, 01:52 AM |#10  
Junior Member
Thanks Meter: 1
 
More
if you ever have problems try nexus root toolkit. It works wonders if you ever severely mess up any nexus device.
14th February 2014, 02:34 AM |#11  
Richieboy67's Avatar
Senior Member
Flag CT
Thanks Meter: 353
 
Donate to Me
More
Wug is also really good for this.

Sent from my Nexus 4 using xda app-developers app

Read More
Post Reply Subscribe to Thread

Tags
bootloader, brick, deb
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes