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
jahames said:
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
Click to expand...
Click to collapse
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
StuMcBill said:
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
Click to expand...
Click to collapse
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
jahames said:
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
Click to expand...
Click to collapse
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?
StuMcBill said:
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?
Click to expand...
Click to collapse
Was working with the 4.4.2 image. Going to give the 4.4 a shot now
Same thing with 4.4...still stuck with the flo bootloader
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?
jahames said:
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?
Click to expand...
Click to collapse
You flashed a recovery for flo. Flash one for deb.
Edit:
http://techerrata.com/browse/twrp2/deb
Reasonably sure I had a deb recovery, but apparently redownloading and reflashing the CWM image did the trick. Thanks!
if you ever have problems try nexus root toolkit. It works wonders if you ever severely mess up any nexus device.
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
same issue
Richieboy67 said:
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
It is here
http://www.wugfresh.com/
It is a toolkit that makes these things very easy. I have used this many times and have never had any issues with it.
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
LinearEquation said:
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Richieboy67 said:
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Click to expand...
Click to collapse
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
LinearEquation said:
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
Click to expand...
Click to collapse
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Richieboy67 said:
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Click to expand...
Click to collapse
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
LinearEquation said:
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
Click to expand...
Click to collapse
While not disastrous, I kind of know what you mean, I started with Wug's (and it is a great toolkit), but once I flashed my own kernel (I used francos app to autoflash so did not have to use recovery or fastboot), I did not realize that by using Wug's a week later that it would flash over that kernel to run those commands and NOT replace francos (I found I was back on stock), lucky by then I had learned enough to recover and no damage was done, but it does point out that my reliance had caused me more work and a bit of worry in the long run.
Still Wug's NRT is a great toolkit...but it should be used as a tool, not a replacement for knowing what to do without it.
Related
I could use some help so I don't brick my phone. I have done a search or two on how to root this particular build and it's probably me - I don't think I have found any information to my question. On xda there was info on the superboot method from modaco that it only worked on ICS4.0.1. The GNex toolkit v7 does not have build IMM30d included. I purchased the phone from Google play and received it late last week. Is this build supported by any root method mentioned? Or will anyone link me to a method that supports the build?
My signature will get you running in a jiffy, sir.
Are you familiar with the toolkit at all?
dirtyreturn said:
Are you familiar with the toolkit at all?
Click to expand...
Click to collapse
for the love of all things good and holy... dont use the toolkit or you'll ask silly questions like this: http://forum.xda-developers.com/showthread.php?t=1747639
dirtyreturn said:
Are you familiar with the toolkit at all?
Click to expand...
Click to collapse
Don't use toolkits. It's not that there is anything inherently bad with them, but having a program do everything for you without understanding how it is doing it means that you don't know how to fix anything if something goes wrong. It's better to do things manually and learn how everything works before taking the easy way through it.
Haha, alright. This is in the Q&A section and I'm sure as hell no developer. I'm coming from a mytouch4g. Had to use adb to downgrade from gingerbread to froyo to root it. Even after reading it over a couple times the directions were still intimidating. It looked like an easy option. Appreciate the input though.
I'll reiterate what others said...
You'll want to know that adb and fastboot are set up correctly, anyway.
They're EXTREMELY useful in countless situations.
I promise you that it'll be an easy process.
Jubakuba said:
I'll reiterate what others said...
You'll want to know that adb and fastboot are set up correctly, anyway.
They're EXTREMELY useful in countless situations.
I promise you that it'll be an easy process.
Click to expand...
Click to collapse
Appreciate the link/input you posted. I'll follow it correctly I hope as it doesn't appear to be rocket science.
Zepius said:
for the love of all things good and holy... dont use the toolkit or you'll ask silly questions like this: http://forum.xda-developers.com/showthread.php?t=1747639
Click to expand...
Click to collapse
hey thanks for rating this one star. :good:
dirtyreturn said:
hey thanks for rating this one star. :good:
Click to expand...
Click to collapse
wasnt me that did that. i dont rate threads.
dirtyreturn said:
hey thanks for rating this one star. :good:
Click to expand...
Click to collapse
Might not have been him...
There's someone(s) bum-rushing the forum today and rating everything 1*.
Jubakuba said:
Might not have been him...
There's someone(s) bum-rushing the forum today and rating everything 1*.
Click to expand...
Click to collapse
Zepius said:
wasnt me that did that. i dont rate threads.
Click to expand...
Click to collapse
HA. sorry. if you are still willing to help real quick... the command 'adb reboot bootloader' brought up a bubble installing device driver.. android 1.0.. failed to install driver. I had already had the drivers installed. Idea?
Most likely, if you connect you device to Wi-Fi, it will receive an OTA update -- I think IMM76 (blanking on build number).
dirtyreturn said:
HA. sorry. if you are still willing to help real quick... the command 'adb reboot bootloader' brought up a bubble installing device driver.. android 1.0.. failed to install driver. I had already had the drivers installed. Idea?
Click to expand...
Click to collapse
The driver needs to install TWICE: once when your device is booted normally, and once when booted into the bootloader.
I'm having a problem using juba's rooting method. It won't go into recovery mode. I'm using the same android and build as the fellow poster. Any help? It's just sticking on the google word with the unlock thing at the bottom when I try to reboot into recovery from the bootloader.
Hold down vol+ and vol- and turn the phone on. When the menu comes up, select recovery.
I know this question has been answered hundreds of times but I can't figure this out on my own. I used the stickies above and it still wont work
I went to flash MMuzy Rom and i flashed the ToroPlus instead of Toro and my Clockwork mod deleted my back up.
ADB Wont push to my phone for some reason either, a list of prompts comes up in the CMD promp.
Please please help
Thanks
did you wipe before flashing the rom?
syntax for adb
adb push c:\locationoffile\file.zip \sdcard\
Yes I did and i used that and nothing, I am trying to use the GNEX Tool but it is stuck on Waiting for Device
good god. not another toolkit user.
you need to install the correct drivers.
Zepius said:
good god. not another toolkit user.
you need to install the correct drivers.
Click to expand...
Click to collapse
I don't usually use the tool kit
I made a human mistake and flashed the wrong rom.
Zepius said:
good god. not another toolkit user.
you need to install the correct drivers.
Click to expand...
Click to collapse
didnt you hear?
every time someone uses the toolkit, an angel gets its wings....
using the toolkit will stop world hunger and provide world peace....
using the toolkit absolves anyone of needing ANY knowledge to actually troubleshoot or fix their device....
screenkeyx said:
I don't usually use the tool kit
I made a human mistake and flashed the wrong rom.
Click to expand...
Click to collapse
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
How can I use this when my phone won't actually boot? I am in clockwork mod and my phone wont pop up on my computer
screenkeyx said:
How can I use this when my phone won't actually boot? I am in clockwork mod and my phone wont pop up on my computer
Click to expand...
Click to collapse
did you even read it?
no you couldnt have since you didnt even read the part of using the bootloader (fastboot) to flash everything.
Zepius said:
did you even read it?
no you couldnt have since you didnt even read the part of using the bootloader (fastboot) to flash everything.
Click to expand...
Click to collapse
Sorry I am extremely stressed out of this and have skimmed it a lot due to people walking in and out of my office
Pirateghost said:
didnt you hear?
every time someone uses the toolkit, an angel gets its wings....
using the toolkit will stop world hunger and provide world peace....
using the toolkit absolves anyone of needing ANY knowledge to actually troubleshoot or fix their device....
Click to expand...
Click to collapse
I heard that if you enter "up up down down left right left right b a start select" into the toolkit it gives your phone infinite RAM.
Issue resolved.
I used the Gnex tool and restored with fast boot.
Thanks for the not funny joke
.....
Zepius said:
good god. not another toolkit user.
you need to install the correct drivers.
Click to expand...
Click to collapse
OMG he used a tool kit, he's so inferior. You might as well call him stupid...
cctoro said:
OMG he used a tool kit, he's so inferior. You might as well call him stupid...
Click to expand...
Click to collapse
Lazy or ignorant would be more accurate. Probably a bit of both.
cctoro said:
OMG he used a tool kit, he's so inferior. You might as well call him stupid...
Click to expand...
Click to collapse
and he learns nothing by using it so he cant even troubleshoot basic problems
Zepius said:
and he learns nothing by using it so he cant even troubleshoot basic problems
Click to expand...
Click to collapse
You know I always thought this community was a good spot to ask questions and get help.
Seems like you guys are no different than fanboys on an Iphone forum.
Have fun jerking your phones off in ADB settings and SDK
screenkeyx said:
You know I always thought this community was a good spot to ask questions and get help.
Seems like you guys are no different than fanboys on an Iphone forum.
Have fun jerking your phones off in ADB settings and SDK
Click to expand...
Click to collapse
Actually this is a developers website.
Not a support forum for making your device cool
Sent from my Nexus 7 using Tapatalk HD
screenkeyx said:
You know I always thought this community was a good spot to ask questions and get help.
Seems like you guys are no different than fanboys on an Iphone forum.
Have fun jerking your phones off in ADB settings and SDK
Click to expand...
Click to collapse
you know i always thought people who came to this site were willing to learn and better themselves with knowledge
seems like you (and most users now days) are no different. unwilling to learn and even accept answers given to you.
have fun relying on toolkits to get you out of trouble. you will receive no more help from me.
Will I really lose my warranty if I unlock the bootloader and install custom ROMS?
And will I get back my warranty if I relock the boot loader and flash stock ROM?
Asus can't see I flashed my device in the past if I have stock ROM with locked bootloader, can they?
Can anyone tell me how this works exactly?
Everywhere I read I MAY risk to lose warranty.
Thanks in advance!
danielsinnema said:
Will I really lose my warranty if I unlock the bootloader and install custom ROMS?
And will I get back my warranty if I relock the boot loader and flash stock ROM?
Asus can't see I flashed my device in the past if I have stock ROM with locked bootloader, can they?
Can anyone tell me how this works exactly?
Everywhere I read I MAY risk to lose warranty.
Thanks in advance!
Click to expand...
Click to collapse
No (well...can go either way)
Yes (although you don't really lose it in the first place)
Once you've flashed the factory image and relocked the bootloader, no they can't (only Nexus to have a tamper flag is the N5)
That warning is standard on all unlockable devices. It's a standard disclaimer they put on there just like any other company would (to cover their butts). However, I do see where the company is coming from. I've seen noobs unlock and start flashing, and then end up messing their device up beyond recovery. They then feel they have the right to get it repaired free of charge. If you know what you are doing, chances are good you'll be fine. If something is actually defective, and as long as you still have to ability to flash stock image and relock, you're good. That being said, I've also read stories of people getting RMAs successfully even though they were unlocked/rooted/ROMed. As long as you can make a case that the defect wasn't caused by your own doing, I would imagine you'd be okay.
charesa39 said:
No (well...can go either way)
Yes (although you don't really lose it in the first place)
Once you've flashed the factory image and relocked the bootloader, no they can't (only Nexus to have a tamper flag is the N5)
That warning is standard on all unlockable devices. It's a standard disclaimer they put on there just like any other company would (to cover their butts). However, I do see where the company is coming from. I've seen noobs unlock and start flashing, and then end up messing their device up beyond recovery. They then feel they have the right to get it repaired free of charge. If you know what you are doing, chances are good you'll be fine. If something is actually defective, and as long as you still have to ability to flash stock image and relock, you're good. That being said, I've also read stories of people getting RMAs successfully even though they were unlocked/rooted/ROMed. As long as you can make a case that the defect wasn't caused by your own doing, I would imagine you'd be okay.
Click to expand...
Click to collapse
Thanks mate for your explanation, I was looking for this.
I have some experience flashing android devices so I probably won't mess up my device I have bought my nexus 7 2013 recently and I don't want to have no warranty when I discover a hardware issue.. But everything seems to be fine actually. I'll install a cm 11 nightly soon.
Sent from my Nexus 7 using xda app-developers app
danielsinnema said:
Will I really lose my warranty if I unlock the bootloader and install custom ROMS?
Click to expand...
Click to collapse
If you should ever need to bring your N7 to the service within the warranty, you will flash a stock ROM, unroot and lock the bootloader. Then you're 100% stock again with no sign of mods.
Do you have a N7 razor 2013?
tetakpatalked from my N7100
tetakpatak said:
If you should ever need to bring your N7 to the service within the warranty, you will flash a stock ROM, unroot and lock the bootloader. Then you're 100% stock again with no sign of mods.
Do you have a N7 razor 2013?
tetakpatalked from my N7100
Click to expand...
Click to collapse
Yes, I think I have that version. I have the wifi only version.
Thanks for the tips man!
danielsinnema said:
Yes, I think I have that version. I have the wifi only version.
Thanks for the tips man!
Click to expand...
Click to collapse
Good. Yes, it is probably razor flo, check to be sure. I have the same one. Just keep in mind to save all your data and settings elswhere as unlocking the bootloader for the first time will instantly wipe whole your tab and poasibly even corrupt the /data partition.
I have written this morning how to get out of it in one other N7 thread.
tetakpatalked from Nexus 7
tetakpatak said:
Good. Yes, it is probably razor flo, check to be sure. I have the same one. Just keep in mind to save all your data and settings elswhere as unlocking the bootloader for the first time will instantly wipe whole your tab and poasibly even corrupt the /data partition.
I have written this morning how to get out of it in one other N7 thread.
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
Yes I see.
I backed up everything in TWRP before I unlocked the bootloader.
I'm now have installed the latest nighty of Cm 11, which is running flawlessly.
Thank you all for telling me how stuff works!
Sent from my Nexus 7 using Tapatalk
danielsinnema said:
Yes I see.
I backed up everything in TWRP before I unlocked the bootloader.
I'm now have installed the latest nighty of Cm 11, which is running flawlessly.
Thank you all for telling me how stuff works!
Click to expand...
Click to collapse
Hey, great mate!
That's why we have a community here.
Don't hesitate to ask if anything.
tetakpatalked from Nexus 7
Yes thank you for creating this thread because then it helps encourage people like me want to root and learn things I want to learn to be a developer when I grow up!
Sent from my Nexus 7 using XDA Premium 4 mobile app
I bought a Nexus 7 today went though all the updates got to 4.4 then checked for updates it told me I was up to date, I know I can just unlock the bootloader and update that way.
thought id ask since it must have a reason to being cancelled
So many threads regarding this issue.
tonyt3rry said:
I bought a Nexus 7 today went though all the updates got to 4.4 then checked for updates it told me I was up to date, I know I can just unlock the bootloader and update that way.
thought id ask since it must have a reason to being cancelled
Click to expand...
Click to collapse
There are a lot of bugs in Lollipop & that the reason why Google might have cancelled the OTA Update. If use Nexus 7 (2013), the good news is that there is a new update 5.0.2 couple of days ago. So you might be receiving the update soon
Thanks I didn't realise that there was so many threads
Sent from my Nexus 5
If you really want the Lollipop update you can use WugFresh's toolkit, you just need to click some buttons and it does everything for you.
JaimerPT said:
If you really want the Lollipop update you can use WugFresh's toolkit, you just need to click some buttons and it does everything for you.
Click to expand...
Click to collapse
Or don't use any toolkit and learn how to use fastboot and adb because they'll help you more than any toolkit.
nhizzat said:
Or don't use any toolkit and learn how to use fastboot and adb because they'll help you more than any toolkit.
Click to expand...
Click to collapse
But for someone that's new to the ecossystem of roms, its a good tool because it does everything for you.
Wugfresh Toolkit is Like Graduation at Primary School. It is necessary for everyone who steps into the world of Rooting, Roms & much more. After sometime, getting the experience, the choice is ours to do
Also, note that the Wugfresh toolkit actually logs every ADB/fastboot command it sends, so you can actually learn a lot by running it and watching it work.
Hi all,
First at all, sorry for my bad English. I'm trying to install Android M's factory image on my Nexus 7, but I'm very lost. Someone could explain me the process step by step? My device isn't root.
Thank you very much.
Use Wug's Toolkit.
^Pretty dangerous recommending a toolkit to someone who has no idea what they're doing.
It'll likely work fine considering it's pretty much a fastboot gui BUT if something goes wrong hes ****ed since he doesn't really know how it works.
OP learn how to use fastboot and flash the factory images there are many guides all over the forums it's very easy. Or wait for the ota.
dangerous recommending NRT ? It's instructions could not be clearer If someone can't properly use it then they can't read simple instructions or understand English
yosmokinman said:
^Pretty dangerous recommending a toolkit to someone who has no idea what they're doing.
It'll likely work fine considering it's pretty much a fastboot gui BUT if something goes wrong hes ****ed since he doesn't really know how it works.
OP learn how to use fastboot and flash the factory images there are many guides all over the forums it's very easy. Or wait for the ota.
Click to expand...
Click to collapse
There is nothing as simply as Wug's toolkit for newcomers so..
might be better off instructing the guy to research the whole entire Android scene before you tell him to toolkit up lol. Google , some research would probably be his best bet
Sent from my Nexus 7 using Tapatalk
Was able!to flsh 6.0. So far so good.
Sent from my Nexus 7 using XDA Premium HD app
Shouldn't N7 2013 running 5.1.1 update to 6.0 with/by OTA? Asking because mine didn't... even with manual check for updates it's reporting no updates available.
flashed! Works great!
strumf666 said:
Shouldn't N7 2013 running 5.1.1 update to 6.0 with/by OTA? Asking because mine didn't... even with manual check for updates it's reporting no updates available.
Click to expand...
Click to collapse
Not yet. I had a OTA update to LMY48T last week. The OTA to 6.0 (from LMY48T) has not appeared yet. Therefore patience - it should happen soon.
Trev
Besides the derp, any issues with video freezing? I reverted back to 5.1.1 as no one seemed to have a clue as to what was causing this.
aiiee said:
Besides the derp, any issues with video freezing? I reverted back to 5.1.1 as no one seemed to have a clue as to what was causing this.
Click to expand...
Click to collapse
Was this on stock kernel or elemental? Video works great for me on stock kernel.
Sent from my Nexus 5 using Tapatalk
tegodwin said:
Not yet. I had a OTA update to LMY48T last week. The OTA to 6.0 (from LMY48T) has not appeared yet. Therefore patience - it should happen soon.
Trev
Click to expand...
Click to collapse
Finally got the OTA upgrade yday