Related
Here I am, what could happen if I flash a kernel for another device that may or may not work with the desire z? I mean will I always be able to boot into CWM and restore a nandroid getting everything work as before?
virtualflyer said:
Here I am, what could happen if I flash a kernel for another device that may or may not work with the desire z? I mean will I always be able to boot into CWM and restore a nandroid getting everything work as before?
Click to expand...
Click to collapse
Yes but it is always possible that you may accidentally fry your motherboard by accident or even brick your device?
Sent from my HTC Vision using XDA Premium App
Sounds bad . How often is this possiblity?
virtualflyer said:
Sounds bad . How often is this possiblity?
Click to expand...
Click to collapse
well it depends. sometimes another devices kernel could mess up the clock settings for your phone as they are not compatible and could accidentally overheat your motherboard. if the kernel you want to use says it has been tested on dz/g2 and works, then it should be fine
It's for a desire hd, it shoulnd't be a problem with the cpu, they're very similar I think
virtualflyer said:
It's for a desire hd, it shoulnd't be a problem with the cpu, they're very similar I think
Click to expand...
Click to collapse
As a general rule you never flash anything that wasnt designed specifically for your device. I strongly recommend against this.
Sent from my HTC Vision using Tapatalk
If you are using a kernel for a different device, flash back. If you are thinking of flashing one, hit yourself in the head a few times and then go flash the tons of amazing G2/Desire Z kernels available.
Sent from my T-mobile G2 using Tapatalk
Just don't flash a kernel not made for the ROM, and especially don't flash a kernel not made for the device. Just don't do it.
No way! Use only kernels for your particular rom.
Sent from my HTC Vision using XDA App
I surely wasn't going to use it, but I needed to try it, so I'll give up. Don't think I'm not using a dz kernel or a kernel made for cyano, or I want a kernel for another device, but I needed to try it.
virtualflyer said:
I surely wasn't going to use it, but I needed to try it, so I'll give up. Don't think I'm not using a dz kernel or a kernel made for cyano, or I want a kernel for another device, but I needed to try it.
Click to expand...
Click to collapse
Its sounds like what you are saying is "I wasn't going to try it, except I was."
What exactly are you trying to accomplish?
redpoint73 said:
Its sounds like what you are saying is "I wasn't going to try it, except I was."
What exactly are you trying to accomplish?
Click to expand...
Click to collapse
Yes, it's a bit like this, just wanted to flash and see what could happen, because of test needings. what I mean is I'm not so crazy that I would daily use a dhd kernel.
Doesn't matter, I won't flash it.
Thanks guys
virtualflyer said:
Yes, it's a bit like this, just wanted to flash and see what could happen, because of test needings. what I mean is I'm not so crazy that I would daily use a dhd kernel.
Doesn't matter, I won't flash it.
Thanks guys
Click to expand...
Click to collapse
What kind of testing? Seeing if you can brick your device? lol. Just don't flash the wrong kernel knowingly. Its just dumb lol.
I remember seeing something about the MT4G, Desire HD, and I think one other phone having the same kernel as the G2/DZ. I know Tiamatt's kernel is based of that idea since we do share the same processor.
Not saying it would work but it *might* be possible to flash a kernel from one of those devices and you'd be ok. Since Tiamatt can make one kernel that works for three different devices, I don't see why one of those devices kernels wouldn't work for ours. It would probably break wifi and be buggy as hell but frying the CPU or motherboard seems like a bit of a stretch.
Now flashing a SGSII kernel may mess some things up but then again, you probably wouldn't get it to boot either so hardware wise you'd be ok. You would however, be the new owner of an expensive paper weight.
I don't advocate flashing kernels across devices just for kicks. But I doubt WWIII will explode out of your G2/DZ either. As long as you stay with a kernel for the same processor. Might be easier to try and compile whatever kernel you want to flash for the G2/DZ....
I've been looking for info about Sprints latest stock ROM but according to most of the info I've found I should still be on JRN84D but I'm on JRO03U. Since the update I lost my root but the boot loader is still unlocked. I've also lost Touchwiz but sounds like I need to go the CWM route anyhow.
Most of the stuff I find on here seems to be referencing Toroplus so I don't want to start adding a recovery that is incompatable or bricking it trying to root with the wrong files. I've also read many times that using the VZW files is a big no no but they are the only ones supporting my build. So any links or info where I can find the info I need would be greatly appreciated. Whats a boy to do?
This is the info you should have with latest rom
Sent from my Galaxy Nexus using xda app-developers app
You lost touchwiz? This isn't a mainstream galaxy phone....
Sent From My Toro+ via White Tapatalk
^^ Yea no Galaxy Nexus variants come with Touchwiz at all. I vaguely remember reading about an effort to bring it over but if I remember correctly it was pretty buggy. So unless you're running that specific custom ROM (and you would definitely know if you were), you never had Touchwiz on this phone.
Definitely don't download any Verizon ROMs or radios. That could brick you. You want "toroplus" builds. That's the sprint variant.
Maybe it wasn't touchwiz. Trying to remember but it was an alternate recovery to CWM that utilized the touchscreen. At any rate I'm back to the stock recovery that is completely useless giving me a droid with a red danger triangle above it.
gagb1967, that is exactly what my build version is. Thats why I'm hesitant to use any of the toroplus files because I know its a mysid build. I've been spending way too much time with my desktop and overclocking because I've forgotten most things about how to mess with my phone. Then again this GNex really doesn't need NEARLY as much alterations as the old Charge and Touch Pro 2 did LOL.
revwolf said:
Maybe it wasn't touchwiz. Trying to remember but it was an alternate recovery to CWM that utilized the touchscreen. At any rate I'm back to the stock recovery that is completely useless giving me a droid with a red danger triangle above it.
Click to expand...
Click to collapse
That's the stock recovery. It's not meant to offer you the same functionality as a custom recovery like TWRP or CWM.
that is exactly what my build version is. Thats why I'm hesitant to use any of the toroplus files because I know its a mysid build. I've been spending way too much time with my desktop and overclocking because I've forgotten most things about how to mess with my phone. Then again this GNex really doesn't need NEARLY as much alterations as the old Charge and Touch Pro 2 did LOL.
Click to expand...
Click to collapse
You have a Sprint model, you can only use Toroplus files.
martonikaj said:
That's the stock recovery. It's not meant to offer you the same functionality as a custom recovery like TWRP or CWM.
You have a Sprint model, you can only use Toroplus files.
Click to expand...
Click to collapse
Thanks all. Back to my good ole rooted stock phone. I can understand using ROM's on other phones because stock interfaces are usually so atrocious but I have yet to find anything wrong with Jelly bean that can't be fixed with an app. Yeah I'm strange LOL. Anyhow thanks again.
Is there anyone developing for the Kindle Fire 2?
As far as I can see, the answer is no but I'm not sure if you're all just been busy and work and don't have much to post yet.
If there is no dev team(s), or devs at all working towards getting this thing with a working Recovery and ROM, I will most likely put together a team this weekend.
Also, assuming there are devs, may you share any findings you have? Why or why not the recovery is being a difficult process and whatnot.
I will probably put together a team just in case, I just can't make promises until I meet this weekend and see if they want to work on this.
If/when i get a team I will make a thread for it and post any news updates as they happen. I really hope we can all get this thing cracked open soon!
Thank you in advance!
UPDATE!:
I hit reply instead of save, so I lost my post sadly, so bullet points!
-I could not contact the main dev.
-I do not plan on making a full dev team anytime soon.
-Powerpoint45 and Hashcode are making progress, moreso Powerpoint, although eventually it seems Hashcode plans to have a workaround, just no ETA or promises from him, but there is more hope than before!
-I will still help and try and offer advice to any newer people, I am not a dev, but I have a decent amount of experience that would be enough to help new people.
Good luck to all!
I too would like to know this. I don't have much but I would donate what I can to the first dev or team to get us past this locked bootloader.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
LegendaryCatalyst said:
I too would like to know this. I don't have much but I would donate what I can to the first dev or team to get us past this locked bootloader.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks I'll let you all know what gets decided this weekend. One coder agreed so far but their experience with Android is limited. The main person I have yet to talk to but he is the one that constantly messes with his android devices since android first came out. The issue is that he does not have a kindle fire, so I may have to buy them ones or lend mine to them to get the coding started.
I have been flashing ROMs and whatnot for a couple years, done my vibrant, galaxy s2, and a few others, but have no coding or developing skills whatsoever. I imagine everyone starts somewhere but I don't have the slightest idea where to begin. I would love to learn though. A locked bootloader seems like a steep challenge compared to obtaining root or developing a ROM. I might be wrong in that regard too.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Depends on how the bootloader is signed. The Motorola Droid and Droid X were relatively easy to crack but other devices may never be cracked without help from the manufacturer.
LegendaryCatalyst said:
I have been flashing ROMs and whatnot for a couple years, done my vibrant, galaxy s2, and a few others, but have no coding or developing skills whatsoever. I imagine everyone starts somewhere but I don't have the slightest idea where to begin. I would love to learn though. A locked bootloader seems like a steep challenge compared to obtaining root or developing a ROM. I might be wrong in that regard too.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Since this device already has Root, I don't know that the bootloader will be an issue. The Gen 1 Kindle Fire has JellyBean running on it already so it may be a (somewhat) simple task to port that to the Gen 2. I'll have to pull it and see what may be device specific to get things running on the Gen 2, but it can be done. We'll need to first get a custom recovery going to allow the ROM to install.
This looks promising from the Gen 1 forum. Perhaps someone can reach out to the dev and see 1) if he's ok with us using it and 2) if he can help get it going on the Gen 2.
http://forum.xda-developers.com/showthread.php?t=1399889
A locked bootloader generally means no custom kernels. Kexec is the only workaround (that I know of) other than unlocking, to start a new kernel . Root simply gives su access, it can't, in and of itself provide kernel customization.
Didn't the recovery for the KFHD's get put on hold? The stock recoveries won't usually let you flash anything that's not signed.
I'm not a dev but it seems like porting the KF1 ROM over to the KF2 should be pretty easy. Other than the bootloader, the hardware changes were minor, just bumping the CPU/GPU up one model and doubling the RAM. Again, it all hinges on unlocking the bootloader or reverse engineering the key it's signed with. Anybody have access to Amazon's EC2 system?
Antoine.WG said:
Didn't the recovery for the KFHD's get put on hold? The stock recoveries won't usually let you flash anything that's not signed.
I'm not a dev but it seems like porting the KF1 ROM over to the KF2 should be pretty easy. Other than the bootloader, the hardware changes were minor, just bumping the CPU/GPU up one model and doubling the RAM. Again, it all hinges on unlocking the bootloader or reverse engineering the key it's signed with. Anybody have access to Amazon's EC2 system?
Click to expand...
Click to collapse
I just toured google today and made a new friend. He doesn't work on the android side, and that building is the most secure on the campus (That and the google+ are the only buildings regular employees can't enter fully without special permissions)
I am hoping he can introduce me to people on the android side of things and see if they would be willing to offer any insight that wouldn't involve an NDA heh.
LaserChicken said:
A locked bootloader generally means no custom kernels. Kexec is the only workaround (that I know of) other than unlocking, to start a new kernel . Root simply gives su access, it can't, in and of itself provide kernel customization.
Click to expand...
Click to collapse
This is true, however the question was around custom ROMS, not kernels. You do not need a custom kernel to run a custom ROM, it's just nice to have the flexability.
Has anyone tried a Kindle fire HD rom? I think the specs are identical except for the screen. I'll do a little research and see what I can do. I would like to see otg working on my son's 2nd generation fire. Sent from my Nexus 7 using Tapatalk HD
I might make a kf2 root app
tjmack3rd said:
Has anyone tried a Kindle fire HD rom? I think the specs are identical except for the screen. I'll do a little research and see what I can do. I would like to see otg working on my son's 2nd generation fire. Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
That's not quite how it works. I would also recommend to NOT TRY ANYTHING ON THE OTHER KINDLE FORUMS. If you check here, people have posted what works. I believe there is one guide for the basic rooting, and another for the steps on using root to make your Kindle do some decent stuff (new launchers, lockscreens, marketplace, all the good stuff!)
However, the issue with the KF2 is not really getting ROMs on, it's the step before it which is getting a working recovery so we can safely flash ROMs onto the device. Once that's done it shouldn't be hard to get a ROM, and it may be even possible to just use a KFHD ROM without any issues, BUT we need the recovery on here first, and getting around the locked bootloader.
To my all caps warning, just check the Q & A forums to see all the people who tried the recovery, rom, and rooting methods for their KF2. Most end up bricked.
If you are experienced in the sort of thing, go ahead and try at your own risk, just be careful. As you may notice, yes, most if not all (can't remember off the top of my head) of the methods we use to root ARE from the KFHD, so yes, some things do work, but way too many times I read about people that tried to put software that wasn't for the KF2 on it and it ends up bricked. Thankfully people seem to be fixing the bricked Kindles, but it's a very unfortunate experience people shouldn't have to go through.
powerpoint45 said:
I might make a kf2 root app
Click to expand...
Click to collapse
Forgot to multi quote :\
This would be great I think! We have the tools so far, it's just that none have been made specifically for the KF2.
Good luck on the app as I'm sure many new KF2 users will appreciate it!
iytrix said:
That's not quite how it works. I would also recommend to NOT TRY ANYTHING ON THE OTHER KINDLE FORUMS. If you check here, people have posted what works. I believe there is one guide for the basic rooting, and another for the steps on using root to make your Kindle do some decent stuff (new launchers, lockscreens, marketplace, all the good stuff!)
However, the issue with the KF2 is not really getting ROMs on, it's the step before it which is getting a working recovery so we can safely flash ROMs onto the device. Once that's done it shouldn't be hard to get a ROM, and it may be even possible to just use a KFHD ROM without any issues, BUT we need the recovery on here first, and getting around the locked bootloader.
To my all caps warning, just check the Q & A forums to see all the people who tried the recovery, rom, and rooting methods for their KF2. Most end up bricked.
If you are experienced in the sort of thing, go ahead and try at your own risk, just be careful. As you may notice, yes, most if not all (can't remember off the top of my head) of the methods we use to root ARE from the KFHD, so yes, some things do work, but way too many times I read about people that tried to put software that wasn't for the KF2 on it and it ends up bricked. Thankfully people seem to be fixing the bricked Kindles, but it's a very unfortunate experience people shouldn't have to go through.
Click to expand...
Click to collapse
I burnt out my usb port trying to make a fastboot cable. I tied the wrong pin in... I'm waiting on my replacement. I'm going to try to use the revrom to get the cwm on my kf2 if that works, I'm sure we could get someone to make a touch cwm or twrp for the kfhd. If the kfhd cwm works, we could use the touch cwm/twrp. Perhaps it will need to be modified... perhaps not. I suspect that the cwm won't work perfectly and we need to modify it to use the correct partition table.
I should mention that using my current factory cable, I can get to fastboot. I just burnt out the data pin. I tried to use dd to flash the revboot stuff, but I forgot to do the part where you get past the locked bootloader... instabrick
fmkilo said:
I burnt out my usb port trying to make a fastboot cable. I tied the wrong pin in... I'm waiting on my replacement. I'm going to try to use the revrom to get the cwm on my kf2 if that works, I'm sure we could get someone to make a touch cwm or twrp for the kfhd. If the kfhd cwm works, we could use the touch cwm/twrp. Perhaps it will need to be modified... perhaps not. I suspect that the cwm won't work perfectly and we need to modify it to use the correct partition table.
I should mention that using my current factory cable, I can get to fastboot. I just burnt out the data pin. I tried to use dd to flash the revboot stuff, but I forgot to do the part where you get past the locked bootloader... instabrick
Click to expand...
Click to collapse
I was trying to make a fb cable earlier today but the connectors were too hard to solder so I need a new cable to work with. I had same idea as u. Trying to boot into a recovery like cwm
Sent from my DROIDX using xda app-developers app
Nvm
you should be able to delete a post...
powerpoint45 said:
I was trying to make a fb cable earlier today but the connectors were too hard to solder so I need a new cable to work with. I had same idea as u. Trying to boot into a recovery like cwm
Sent from my DROIDX using xda app-developers app
Click to expand...
Click to collapse
I bought one on eBay for £3 including free next day delivery. I'll try to find the link as he was selling lots and it was delivered fast (in UK).
EDIT :
http://item.mobileweb.ebay.co.uk/viewitem?itemId=140893291002
Sent using my Jelly fingers.
Not devving yet, but as soon as we have our own recovery...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Firstly, love the tablet. However, the whites could be better. Would a custom rom help make them whiter? Or is that totally a hardware dependent thing? Unrelated, but is there a way to remove stock lg apps? I thought for sure i read somewhere that you can without rooting, but cant seem to find the option anywhere. Thanks
supremekizzle said:
Firstly, love the tablet. However, the whites could be better. Would a custom rom help make them whiter? Or is that totally a hardware dependent thing? Unrelated, but is there a way to remove stock lg apps? I thought for sure i read somewhere that you can without rooting, but cant seem to find the option anywhere. Thanks
Click to expand...
Click to collapse
@YoungBobbie has made a kernel for the 500 device which may take care of the screen problem. His thread is in the development section for downloads and updates. You will need a custom recovery like twrp to use his kernel. There is also another person working on a 500 kernel as well that may be available soon.
sleekmason said:
@YoungBobbie has made a kernel for the 500 device which may take care of the screen problem. His thread is in the development section for downloads and updates. You will need a custom recovery like twrp to use his kernel. There is also another person working on a 500 kernel as well that may be available soon.
Click to expand...
Click to collapse
Sweet. 'Thanks' coming your way. I've seen the root method for the g pad. And it seems that the method bypasses unlocking the boot loader. Is it the same with flashing a custom recovery and Roms? No boot loader unlocking needed? Don't mean to go ot, but I figured I'd pick your brain instead of starting a new thread. Thanks again
Hello everyone!
I just don't get it. Can anyone explain to me what's the difference between flashing a bumped rom and flashing the same rom un-bumped? I just don't get the whole point of it! Sorry, but coming from a Nexus device (why have I ever changed!!!) I'm new to these things.
So, other questions would be: what's the point of bumping? What if I don't do it and just go about the usual way: Unlocking the bootloader, rooting and installing a custom recovery and then proceed to flash the appropriate and preferred rom, kernel, etc?
Hope somebody will bear with me and try to explain these things to a newcomer
Thanks
astrovale said:
Hello everyone!
I just don't get it. Can anyone explain to me what's the difference between flashing a bumped rom and flashing the same rom un-bumped? I just don't get the whole point of it! Sorry, but coming from a Nexus device (why have I ever changed!!!) I'm new to these things.
So, other questions would be: what's the point of bumping? What if I don't do it and just go about the usual way: Unlocking the bootloader, rooting and installing a custom recovery and then proceed to flash the appropriate and preferred rom, kernel, etc?
Hope somebody will bear with me and try to explain these things to a newcomer
Thanks
Click to expand...
Click to collapse
Because
1) Bumping is used to trick the bootloader into thinking that the boot.img is authentic and from Official LG Sources
2) Without bumping you could have to constantly run fastboot boot boot.img (an example of this was CM11 when it first started development)
3) Bootloader cant be unlocked at this time so we rely on a bootloader exploit in order to run custom recovery
4) Its all about the authenticity. If the LG bootloader does its security checks and anything fails then the system doesnt boot
Thanks for the very easy tuo understand explanation. I should have thought that the problem was unlocking the bootloader! Guess I'll have to with the Flow and bump my new phone. I wish I asked my Carrier for an HTC M8
Sent from my Xperia Tablet Z LTE using XDA Free mobile app
simple answer: bump is the only way to unlock g3 bootloader.
all roms are bumped whether displaying [BUMPED] or not.
rhystagram said:
simple answer: bump is the only way to unlock g3 bootloader.
all roms are bumped whether displaying [BUMPED] or not.
Click to expand...
Click to collapse
Ok, so by simple logic, once I have installed, either via bump, flashify or ADB a recovery, I can pretty much flash any rom that is appropriate for my model no, isn't it?
So there is one more question I have: what is the purpose of unlocking the bootloader and then what could be the problems if I don't? If everything I flash for this device (TWRP, roms, kernels, etc) is, by default, bumped, what's the purpose of installing bump at all?
astrovale said:
Ok, so by simple logic, once I have installed, either via bump, flashify or ADB a recovery, I can pretty much flash any rom that is appropriate for my model no, isn't it?
So there is one more question I have: what is the purpose of unlocking the bootloader and then what could be the problems if I don't? If everything I flash for this device (TWRP, roms, kernels, etc) is, by default, bumped, what's the purpose of installing bump at all?
Click to expand...
Click to collapse
You're making it so much harder for yourself dude.. There really is only one way to install custom ROMs and that is by Bumping your phone. That's it.
You go here and read the entire topic. Don't miss a single thing.
Then go here and flash the zip for the latest TWRP.
After that you can install any ROM in the OG and Android Development section.
That's all there is to it. You can read in those topics for more information about what they do.
if you dont bump, then you wont have twrp lol.
you cant flash any roms anyway, you'll potentially brick/soft brick your phone.
roms etc are bumped because they have a patch script implanted to run on the phones correctly.
rhystagram said:
if you dont bump, then you wont have twrp lol.
you cant flash any roms anyway, you'll potentially brick/soft brick your phone.
roms etc are bumped because they have a patch script implanted to run on the phones correctly.
Click to expand...
Click to collapse
OK. Got it! It took a while, but I give up!
Thanks for the help. Coming from the most easy to play with phones (only Nexus so far, but I hate the N6), it isn't easy to have to deal with more stuff than usually needed and hence more complications than usually had.
I thought that, after rooting I could flash TWRP via flashify or rom toolbox and then I would have TWRP without BUMP, but it must be that I'm missing something, if you say I MUST bump my phone to install TWRP.
Thanks and see you around
How to bump lg g3
DevilFan14 said:
How to bump lg g3
Click to expand...
Click to collapse
What exactly do you mean "How to bump"??? Bump and loki are bootloader exploits that allowed us to boot TWRP and all the benefits TWRP offers... On the user side of things you don't "Bump" anything- the Roms, Kernels, and recoveries are "pre-bumped" by the developers and 99.9% of the time they will say whether or not it is "bumped" or "lokied" although loki is really outdated and I doubt you'll encounter it. So in a nutshell we(the user) doesn't "Bump" anything and just make sure to really read before flashing
Sent from my DROID RAZR HD using XDA Labs