Related
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
Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.
Can I flash a new bootloader using recovery (twrp)? (flashed plenty of ROMs and Kernels wasn't sure if the steps are the same for a bootloader)
So if I plug my rooted Nexus 7(2013) in to any usb cable on any computer, it is just not detected(assuming usb port is dead at this point, only charges), Cannot even get adbd wifi to start and listen on port 5555 went through every possible scenario.( basically tried everything you can will throw at me, (MTP/PTP, usb debugging on/off, new cables, new computers, remove every possible android driver and re-install)
I saw one post where someone seemed to have a similar issue but was able to update the bootloader and his problem was solved!
Now I am not sure how he did it since I can't seem to find any good info on updating the bootloader directly from say TWRP I have no other access into the device remotely or via USB
kernelsandirs said:
Can I flash a new bootloader using recovery (twrp)? (flashed plenty of ROMs and Kernels wasn't sure if the steps are the same for a bootloader)
So if I plug my rooted Nexus 7(2013) in to any usb cable on any computer, it is just not detected(assuming usb port is dead at this point, only charges), Cannot even get adbd wifi to start and listen on port 5555 went through every possible scenario.( basically tried everything you can will throw at me, (MTP/PTP, usb debugging on/off, new cables, new computers, remove every possible android driver and re-install)
I saw one post where someone seemed to have a similar issue but was able to update the bootloader and his problem was solved!
Now I am not sure how he did it since I can't seem to find any good info on updating the bootloader directly from say TWRP I have no other access into the device remotely or via USB
Click to expand...
Click to collapse
Yeah it's possible, I did it for the Nexus 4 before. Usually the bootloader update files are found within the OTA zip updates. Usually the bootloader is composed of multiple files, not just one. You can take those files and put them in a flashable zip and make sure the script flash the files to the correct partition of the device, all the info are in the updater-script file in the zip.
It look like this is the last OTA update for the N7 that have the bootloader files: http://android.clients.google.com/p....signed-razor-KTU84L-from-KOT49H.df43279b.zip
So you can use make a flashable zip for those bootloader files or I can do it later.
I guess a smarter person would be able to dump these partitions from their device, maybe just by using "dd" command while in recovery's ADB.
I previously flashed a pre-rooted 4.4.4 OTA Stock ROM which is what I have been running ever since.
I really don't know if, or why the bootloader would affect my ability to use the USB port or not, but I guess I just had some hope based on one other post that seemed to work with.
I am not sure how to make a flashable zip from an existing ROM image, only flashable zips I made came from Titanium backup producing the flashable files for me
eksasol said:
Yeah it's possible, I did it for the Nexus 4 before. Usually the bootloader update files are found within the OTA zip updates. Usually the bootloader is composed of multiple files, not just one. You can take those files and put them in a flashable zip and make sure the script is flash it to the correct partition of the device, all these infos are usually found in the official OTA zip. The problem is not all OTA zip have bootloader files, just the one that specifically update it.
It look like this is the last OTA update for the N7 that have the bootloader files: http://android.clients.google.com/p....signed-razor-KTU84L-from-KOT49H.df43279b.zip
So you can use make a flashable zip for those bootloader files or I can do it later.
The next one will be for Android 5, so we'll look forward to that also. I guess a smarter person would be able to dump these partitions from their device or something.
Click to expand...
Click to collapse
So your computer doesn't recognize the tablet when it's at the bootloader? Can you even get into bootloader? Tried different cables? Different USB ports?
I can get to TWRP, but no usb not recognized there, cannot use the mount feature in TWRP, tried all items in pretty much every post I could find that were related, inlcuding the items you suggest yes.
Maybe something with the stock rooted ROM has gone wacky, Been very good to this tablet as far as babying the usb port, as I have had other devices have broken ports as my kids would yank cables etc.
So really the only thing I have not done since this trouble started was just do a factory reset and re-flash the ROM, just afraid that is something goes wrong durring flash I will be out of luck restoring anything since I cannot get to the filesystem to put new ROMS etc unless I download them to SD before I begin the process while I have access to the OS and wifi.
nhizzat said:
So your computer doesn't recognize the tablet when it's at the bootloader? Can you even get into bootloader? Tried different cables? Different USB ports?
Click to expand...
Click to collapse
[snip]
Thanks @eksasol I think I may just let this sucker chill until the stock rooted Lollipop ROM, I was already on 4.02 I just thought there was a newer one, I think the Lollipop version has a 4.04 bootloader.
I greatly appreciate your time on this.
So I would assume that if the flash fails for any reason I will be the proud new owner of a nexus 9 shortly after
@eksasol do you have a flashable 4.04 bootloader or know a guide to making a bootloader flashable, I did use your 4.02 and it worked great, but for the Lollipop version I need 4.04 but can only find .img that needs fastboot, which I do not have access to since USB does not seem to work still.
kernelsandirs said:
@eksasol do you have a flashable 4.04 bootloader or know a guide to making a bootloader flashable, I did use your 4.02 and it worked great, but for the Lollipop version I need 4.04 but can only find .img that needs fastboot, which I do not have access to since USB does not seem to work still.
Click to expand...
Click to collapse
You will need to wait until the OTA zip for KitKat to Lollipop become available, it will include the proper 4.04 bootloader files needed for flashing.
OK cool, guess I am just impatient
@eksasol any chance you can throw a flashable 4.04 bootloader together, i see several others looking for one that are in the same boat as me, i looked around for a tutorial on making one but did not find any so far. Anyway if you get a chance or have some info on making one i would be grateful.
Here is the Android 5.0 bootloader version 4.04. For Nexus 7 WiFi only (Flo, Razor), again it will check to see if it's the correct device before proceeding with flashing. Go to this link: http://forum.xda-developers.com/nexus-7-2013/general/flashable-factory-image-zips-android-5-t2939599
kernelsandirs said:
@eksasol any chance you can throw a flashable 4.04 bootloader together, i see several others looking for one that are in the same boat as me, i looked around for a tutorial on making one but did not find any so far. Anyway if you get a chance or have some info on making one i would be grateful.
Click to expand...
Click to collapse
You didn't have to remind me every single day.
Thanks for this. I'm alright with adb and fastboot (i.e. I can follow directions) but I'm running the Windows 10 tech preview and it absolutely does not support either. Drivers are fine, it just won't do it. Won't happen at all. Then I throw it all on a flash, take it to work (Win7 Pro), and it works just as easy as you like, so it's not (likely) user incompetence... I woulda waited but figured someone else might have asked. So, much appreciated!
dragontology said:
Thanks for this. I'm alright with adb and fastboot (i.e. I can follow directions) but I'm running the Windows 10 tech preview and it absolutely does not support either. Drivers are fine, it just won't do it. Won't happen at all. Then I throw it all on a flash, take it to work (Win7 Pro), and it works just as easy as you like, so it's not (likely) user incompetence... I woulda waited but figured someone else might have asked. So, much appreciated!
Click to expand...
Click to collapse
They decided to skip 9?
I posted the full device's image in flashable zip formats here:
http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/
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
Hi all,
I have a zenfone 2 that I have just rooted....so now what?
Basically I wanted to optimise my phone so I am able to disable annoying notifications which are greyed out (although since rooting and checking this it still greyed out) I want to remove bloatware and I would actually like to customise my own android system, starting from a 'vanilla' base where I can build it up myself.
I have also read that I need to install a android recovery programme on asap after rooting.
So sorry about this but I really do need 'stupid' instructions as using hi tech words will just baffle me. lol
I have played around with computers in the past and learned about them so this is the phone stage now!
Thanks in advance and for your patience with this newbie!
Kerry
Yankeegal said:
Hi all,
I have a zenfone 2 that I have just rooted....so now what?
Basically I wanted to optimise my phone so I am able to disable annoying notifications which are greyed out (although since rooting and checking this it still greyed out) I want to remove bloatware and I would actually like to customise my own android system, starting from a 'vanilla' base where I can build it up myself.
I have also read that I need to install a android recovery programme on asap after rooting.
So sorry about this but I really do need 'stupid' instructions as using hi tech words will just baffle me. lol
I have played around with computers in the past and learned about them so this is the phone stage now!
Thanks in advance and for your patience with this newbie!
Kerry
Click to expand...
Click to collapse
Hi Kerry,
First thing you should now do after rooting your device would be flashing a custom recovery that is specific to your device (make sure your devices boot loader is unlocked first). This will allow you to make a backup of everything just in case anything were to go wrong, flash custom ROMs and useful zips. You can pick your favorite custom recovery such as Team Win Recovery Projects custom recovery (TWRP), Clock Work Mods custom recovery (CWM) or Philz Touch recovery based off of CWM although personally I would recommended twrp.
There are multiple ways to do this: Using the TWRP/CWM recovery installer from the play store or the more complicated way of flashing it from your computer. If you were to choose to install TWRP from their app on the play store (grant it root permission) you can select your device from the supported device section within the app, pick the latest recovery, hit the install button and let the app work its magic. If all works correctly you can now reboot to recovery and you will see TWRP is installed. Now you should create a backup to be on the safe side and you're good to go!
To best optimize your device I would recommend installing a custom ROM (look up custom ROMs for the Zenfone 2) and install the zip through recovery. (make sure to pick the right ROM for your device and version otherwise you may soft brick your smartphone) Now with a custom ROM you can better optimize your device and fully customize it to your liking. Make sure to look up custom ROM installation instructions for your device for better detail.
As far as removing system apps/bloatware you can use a "root app delete" tool from the play store but be careful what you remove as some applications are required!
Make sure to take your time and be careful when attempting any of these things and be careful what you modify! Just remember that no question is a stupid question as we all have to start somewhere!
Hope I was able to help you even if it was just a little, good look and have fun!
Rooted Droid Thanks you so much!!! First of all thanks for being so patient with me and secondly thanks for the useful (and easy to read) information.
I will go and install a back up on my phone from the ones you have suggested.
Hopefully you will be around over the next few days if I have more questions. Not planning on doing this all at once but rather taking the time and doing it right.
Thanks so much again!! :good::good::good:
Ooops sorry....how do I do this please?? ---> (make sure your devices boot loader is unlocked first)
Yankeegal said:
Rooted Droid Thanks you so much!!! First of all thanks for being so patient with me and secondly thanks for the useful (and easy to read) information.
I will go and install a back up on my phone from the ones you have suggested.
Hopefully you will be around over the next few days if I have more questions. Not planning on doing this all at once but rather taking the time and doing it right.
Thanks so much again!! :good::good::good:
Click to expand...
Click to collapse
Not a problem! I'm always happy to spread some knowledge and appreciate when people do the same to me! I also went ahead and checked the TWRP app and the Zenfone 2 is supported so it looks like your good to go. And yes absolutely, there's no rush so take all the time you may need and everything will go smoothly! I'm always around and will try my best to answer questions.
---------- Post added at 08:02 AM ---------- Previous post was at 07:41 AM ----------
Yankeegal said:
Ooops sorry....how do I do this please?? ---> (make sure your devices boot loader is unlocked first)
Click to expand...
Click to collapse
Check this site out:
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
All devices have a different method for unlocking bootloader (some don't even have locked bootloaders) but this is an official bootloader unlocking method for the Zenfone 2 from Asus itself. I suggest following its directions and you should be able to unlock it this way.
Ok I followed the link but now I am confused. I have version ww_2.20.40.63_201......
Apparently I need a later version. What started off with just adding an APP means me doing other things before I even get to that point (hence the confusion! lol)
I never updated the phone via OTA as I was told it would invalidate my warranty and also I have killed a phone before using that so can you walk me through please...if you have the time....or could I just check if I have it unlocked already??
I haven't even gotten to the part where I create a backup...tee hee
Yankeegal said:
Ok I followed the link but now I am confused. I have version ww_2.20.40.63_201......
Apparently I need a later version. What started off with just adding an APP means me doing other things before I even get to that point (hence the confusion! lol)
I never updated the phone via OTA as I was told it would invalidate my warranty and also I have killed a phone before using that so can you walk me through please...if you have the time....or could I just check if I have it unlocked already??
I haven't even gotten to the part where I create a backup...tee hee
Click to expand...
Click to collapse
Hi sorry for the late reply, I'm in Canada so it was 2am when I was last talking to you so I went to bed haha. Anyway as far as unlocking the Zenfone 2's bootloader I wouldn't have experience unfortunately as I'm using a Nexus 5. The easiest way to go about this now would be to go to your device specific forum and find a way to unlock it there.
The following way to unlock the bootloader requires you have ADB installed on your PC. This is a guide for installation on Windows :
http://www.android.gs/install-android-sdk-adb-windows/
And here is a thread specific to unlocking the Zenfone 2 using adb:
http://www.xda-developers.com/asus-zenfone-2-bootloader-unlocked-without-asus/
BTW as you mentioned "updating may invalidate your warranty" things like rooting, installing a custom OS, unlocking the bootloader, installing a custom recovery and other things like that all (in most cases) void your warranty.
Sorry I can't personally help with the bootloader as I've not personally unlocked it on a Zenfone. Still feel free to ask any questions if you need to. Good luck!