Develop Bugs

Galaxy nexus 4.0.4 build IMM30d root

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.

[Q] May have bricked my N7 (deb)

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.

Flashfire supporting Pixel (XL)?

Hi
Does anyone know anything a out the current status of Flashfire on the Pixel (XL)?
I've tried to backup data and the screen turned black, afterwards I hard to hard reset the phone to get it working again.

niko26 said:
Hi
Does anyone know anything a out the current status of Flashfire on the Pixel (XL)?
I've tried to backup data and the screen turned black, afterwards I hard to hard reset the phone to get it working again.
Click to expand...
Click to collapse
Good place to start https://plus.google.com/+Chainfire

danw_oz said:
Good place to start https://plus.google.com/+Chainfire
Click to expand...
Click to collapse
I've tried to contact him already, plus asked him in one of his threads/posts. No response.

niko26 said:
I've tried to contact him already, plus asked him in one of his threads/posts. No response.
Click to expand...
Click to collapse
It's probably because he got sick of being asked the same question over and over again.
If I read the XDA forums http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 searching for the word PIXEL. This app appears that people have this working on Pixel XL, but not since the November release

danw_oz said:
It's probably because he got sick of being asked the same question over and over again.
If I read the XDA forums http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 searching for the word PIXEL. This app appears that people have this working on Pixel XL, but not since the November release
Click to expand...
Click to collapse
Thanks for your comment.
I was not asking why he was not replying to my questions - I've got total sympathy for that because the number of messages he might get must be insane.
My question still stands: Obviously Flashfire is not yet aware of the different layout of partitions on the Pixel phones. Does it still work correctly? If not, did Chainfire say anything about Flashfire being fixed to work with the pixels? I couldn't find anything, that's why I'm asking here.

I assume any announcement on it working on the Pixel will be made when it works on the Pixel. Much like superSU. (hope that doesnt sound like an ass thing to say) it's just the way things have been. unless someone else works on something and it looks like they are going to beat another dev to the punch, you don't usually see any info, much like boot-loader unlocks, rooting of a certain phone etc.. i.e when there is a bounty and team blahblah looks like they gonna take the glory, BANG! suddenly there's a solution that said dev was already working on secretly but wasn't planing on releasing any time soon but since there's competition, kinda thing. Know what I mean?

SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.

larsdennert said:
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
Click to expand...
Click to collapse
Hey just curious what you mean by this. I know that TWRP has some bugs but I thought everything with SuperSU was worked out

I'm thinking they are still working on having them coexist without one wiping the other

larsdennert said:
I'm thinking they are still working on having them coexist without one wiping the other
Click to expand...
Click to collapse
No they work fine, especially SuperSU. TWRP is in alpha but works for installing and most other things but backup and restore does not yet.

larsdennert said:
I'm thinking they are still working on having them coexist without one wiping the other
Click to expand...
Click to collapse
Wow, that was like week number one.
You're waaaaaay behind on updates.

Lol then we should get on chain fires case

larsdennert said:
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
Click to expand...
Click to collapse
What? SuperSU working perfectly with twrp. As others said twrp still in alpha and some features are iffy, but SuperSU is solid.

Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?

s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
Are you verizon?
Because if you're verizon then add Verizon to your profile so people can appropriately address your questions.
And add your freaking state/country while you're at it. :good:

CZ Eddie said:
Are you verizon?
Because if you're verizon then add Verizon to your profile so people can appropriately address your questions.
And add your freaking state/country while you're at it. :good:
Click to expand...
Click to collapse
My apologies. T-Mobile, US - added to profile. Thanks for the suggestion!

s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
You can sideload the update via ADB supposedly.
I've never used that method though.
I just flash the entire update on top of my old OS using flashboot and my guide here:
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Make sure to remove the -w from the script if you don't want your old data/apps wiped.
Then re-root your phone afterwards.
Nothing to worry about there if it's not a Verizon phone.

s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
I do it like in this guide http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/

Very helpful, thanks guys. I did it and it worked - ran flash-all with -w removed. I wonder though if there's any downside to doing this that may not have been identified yet, such as extra space being taken up or diminished performance (even if negligible) possibly due to some duplication of data or something like that.

s1dest3pnate said:
Very helpful, thanks guys. I did it and it worked - ran flash-all with -w removed. I wonder though if there's any downside to doing this that may not have been identified yet, such as extra space being taken up or diminished performance (even if negligible) possibly due to some duplication of data or something like that.
Click to expand...
Click to collapse
No, no downside at all. Flash all without the -w is how most people do it. It could even be argued that it is better.
Sent from my Pixel XL using XDA Labs

Root without PC

Is there a way to root without PC. I googled it but what I found was almost a year old so I wasn't sure if anything has changed.

UnicornHub said:
Is there a way to root without PC. I googled it but what I found was almost a year old so I wasn't sure if anything has changed.
Click to expand...
Click to collapse
Nope. You need a pc to unlock the bootloader so you can then root your device. Sorry man.

Badger50 said:
Nope. You need a pc to unlock the bootloader so you can then root your device. Sorry man.
Click to expand...
Click to collapse
Dang ok. I saw the all in one toolbox's are those stable and do they work well? If not what's the best easiest root method

UnicornHub said:
Dang ok. I saw the all in one toolbox's are those stable and do they work well? If not what's the best easiest root method
Click to expand...
Click to collapse
I've never used a toolkit. I prefer the manual method with my pc and fastboot commands. Here's a great guide to help you on your way :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

Yes knowing how to do it manually is the best way typically I've tried a few all in ones and some reason usually have issues also some make it too easy to mess it up if I don't know what you are doing and hey inpatient
Sent from my Pixel 2 XL using Tapatalk

gjkrisa said:
Yes knowing how to do it manually is the best way typically I've tried a few all in ones and some reason usually have issues also some make it too easy to mess it up if I don't know what you are doing and hey inpatient
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure that even with one click root methods, you'll still need an unlocked bootloader.

Yeah true
xunholyx said:
I'm pretty sure that even with one click root methods, you'll still need an unlocked bootloader.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

Don't rely on the "AIO" Toolkits or the "One Click Root" Toolkits. I do appreciate the developers' effort they put in these toolkits to make people's life easier however many times they are outdated and don't work as they should and are just causing headache. Use Fastboot and ADB and nothing can go wrong! If something does, well... There are so many extremely nice people here who are willing to help you out, answer your questions and bring your phone back to life! Khm... @Badger50 just to mention one! Khm...

True, with oneclick root you must still have an unlocked bootloader otherwise i won't work.

New update and rooted Pixel 3 XL How to?

Hi all,
Pixel 3 XL
Android 10(QP1A.190711.020)
ELEMENTALX-P3-2.05
Have a look at attached screenshots, how would one apply the new update without messing it up, i finally have GPay working, and I really want to keep it that way.
Thanks
I cant seem to be able to upload attachments, "url can not prase" ?

Not sure about keeping Google pay, but I followed A/B slot update from here https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
Everything is working fine on QP1A.190711.020.C3
You will need to reflash the kernel.
Only using systemless hosts and edge sense modules in magisk.

rob42ert said:
Hi all,
Pixel 3 XL
Android 10(QP1A.190711.020)
ELEMENTALX-P3-2.05
Have a look at attached screenshots, how would one apply the new update without messing it up, i finally have GPay working, and I really want to keep it that way.
Thanks
I cant seem to be able to upload attachments, "url can not prase"
Click to expand...
Click to collapse
How'd you get Google Pay working?
I flashed the complete system img removing the -w and re-rooted (pulled boot.img from the zip and had magisk patch it and flash in fastboot)

rquinn19 said:
How'd you get Google Pay working?
I flashed the complete system img removing the -w and re-rooted (pulled boot.img from the zip and had magisk patch it and flash in fastboot)
Click to expand...
Click to collapse
Gpay i got it working with BostonDan method.

Can you please link Boston Dan method?

skaforey said:
Can you please link Boston Dan method?
Click to expand...
Click to collapse
pretty easy to google BostonDan and Google Pay. First result. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Edit: Just tried it on my rooted Android 10 3XL and I was able to add my cards. Haven't used it yet but generally if I can add cards I can use it. Thanks

henderjr said:
pretty easy to google BostonDan and Google Pay. First result. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Edit: Just tried it on my rooted Android 10 3XL and I was able to add my cards. Haven't used it yet but generally if I can add cards I can use it. Thanks
Click to expand...
Click to collapse
I have been using that method since the day he posted it on a 3 and 3 XL. Both are on 10, and got clean wiped to do so. Both had card reinstalled and have been used at the terminal since the c3 update.

sliding_billy said:
I have been using that method since the day he posted it on a 3 and 3 XL. Both are on 10, and got clean wiped to do so. Both had card reinstalled and have been used at the terminal since the c3 update.
Click to expand...
Click to collapse
Good to hear.! I have a WearOS watch with Google Pay so I haven't had a need to use my phone much.

I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?

rob42ert said:
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
Click to expand...
Click to collapse
How exactly have you determined that it is the kernel, and what does "many bug" mean? There are a lot of us who are using ElementalX on 10 with no issues including assistant squeeze. You can start by installing any other kernel available in the "Google Pixel 3 XL ROMs, Kernels, Recoveries, & Other Development" section (you will need to re-root) and see if it makes any difference. It would also be a good idea if you posted in the dedicated thread for ElementalX. Besides getting user answers, @flar2 will be able to answer any questions specific since it is his kernel.
As for possible issues, how you installed could (dirty, clean, OTA/OTA sideload, factory image in BL) make a very possible difference as well as what version you have installed (specifically if you installed the new c3 image). It sounds like you have a bad Android 10 install and are going to end up needing a full clean install. Good luck.

rob42ert said:
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
Click to expand...
Click to collapse
There are no bugs in ElementalX kernel.