Hey guys, I just ran across this article online. What (if anything) does it mean for the X?
http://www.gadgetsdna.com/milestone-bootloader-hacked-and-broken/3574/
Thanks
cavz903 said:
Hey guys, I just ran across this article online. What (if anything) does it mean for the X?
http://www.gadgetsdna.com/milestone-bootloader-hacked-and-broken/3574/
Thanks
Click to expand...
Click to collapse
The bootloader isn't cracked. That article jumped the gun.
Mikerrrrrrrr said:
The bootloader isn't cracked. That article jumped the gun.
Click to expand...
Click to collapse
But theres a few ROMs available for download in the milestone section of XDA. Whats that all about?
cavz903 said:
But theres a few ROMs available for download in the milestone section of XDA. Whats that all about?
Click to expand...
Click to collapse
Please take look this site in attachment. Load a custom ROM by nandroid.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1) Has the bootloader been cracked?
2) if not, how do they have custom roms?
sp1kez said:
1) Has the bootloader been cracked?
2) if not, how do they have custom roms?
Click to expand...
Click to collapse
They have actually been working on a way around it. In essence its not a true hack but more of an exploit, using "kexec" module. What this module does is once the phone to boots up into the stock kernel then you use the kexec module to in essence hot swap to another kernel. Once the phone powers off it goes back to stock, but when you power it on again you would just do the same thing again. Using some combination an something similar to nanadroid you can load custom roms with custom kernals. The only down side is that it would increase boot times, but it would have no impact on the performance of the phone otherwise.
I have been doing alot of reading on the milestone and the progress made and they seem to have the overall workings of this method down its just getting it smooth enough that people can use it. Assuming the Droid X has the same module in the stock kernal we should be able to easily port this once they have it fully working on the milestone!
Nice to have a glimmer of hope.
Sent from my DROIDX using XDA App
Little summary about milestone bootloader crack progress..
now they dont use kexec method anymore..they use 2nd bootloader method
http://www.motorolafans.com/forums/android-dev-talk/30158-2nd-boot-milestone-progress.html
2nd boot for milestone progress ....
This will only work on milestone with 2.0 system on it so you have to downgrade in order to test this / modify it ...
'modem itself panics, when new kernel try to reestablish netmux links, so even if usb host will work finely - modem still need to be reseted. or netmux module and daemons needed to be patched to work in needed way'
how to :
place in /system/bin , permission set to 755
let phone screen turned on, because this state is closer to original boot
sh hb.sh
http://www.droid-developers.org/files/2ndboot.rar
at least we have a custom kernel booting , modem doesnt work so no radio if you can fix this or have any ideas how to , please join :
#milestone-modding on Freenode (IRC )
http://and-developers.com/motorola_milestone
Custom Rom method:
2ndboot
Usefulness: Very high
Difficulty to attempt:Medium
Chance of success: Very high
Status:
This attack right now is by far the most promising and convenient. Recently a few developers have pursued this approach in at least three independent attempts. All face a significant roadblock: hardware initialization. There are a couple of ideas about tackling it, but it is still a work in progress at the time of this writing. See more information about previous attempts here. None of these attempts work yet!
Latest attempt: Yakk patched 2nd-boot to make it work on the Milestone, but his source code remains partly unpublished at this time. Status: boots another kernel, which Yakk has also patched to get serial output over the USB connector (using custom hardware to connect to it). Currently the booted kernel has some problems with USB and fails to initialize the phone's modem so it crashes. See published code and binaries: here (build number 1.03) and here (build number 2.31). All current development of 2ndboot now going here When GSM is disabled this kexec module is able to boot the system with the recompiled kernel, but it is not really useful as a phone then. WiFi works fine, though. Yakk is now trying to use 2ndboot to start a patched version of mbm, which should be able to initialize the modem and then pass control to a custom Linux kernel. This is still under development, so don't get too excited. We'll keep you posted.
2ndboot
This is bootloader, which can boot custom boot image even droid-family phone has locked bootloader.
It consist from: * small kernel module, for creating device for booting/controlling boot * small userspace program, which give for module boot image and flags * universal bootloader, which can uses many places for booting
It's derived from collaborative work of yakk and dimichxp for creating bootloader for older motorola phones, before their RSA have been kracked.
Now, this project ported to the Milestone hardware and can boot custom kernel fully, except of baseband part.
Here you can find current development sources of 2ndboot: http://bitbucket.org/droiddev/2ndboot/overview
See published binaries: here (build number 1.03) and here (build number 2.31).
Also it is necesseary for developing 2ndboot and custom bootloader/kernel to debug over serial port: Debugging
Click to expand...
Click to collapse
Nice, Huranjo.
I can't wait for someone to take the first SUCCESSFUL step on their X so I don't have to chance breaking mine!!!! : )
cbaty08 said:
Nice, Huranjo.
I can't wait for someone to take the first SUCCESSFUL step on their X so I don't have to chance breaking mine!!!! : )
Click to expand...
Click to collapse
i dont have droid x..i am milestone user but we have a same problem ..lock bootloader...
if milestone bootloader successfully hack..then all motorola locked bootloader product will also hackable too
this is for more detail progress....and i know these guys is very capable and very expert about reverse engineering technique..so lets support them..and lets wait for result..
http://bitbucket.org/droiddev/2ndboot/overview
Age
Author Message A M D « » 7 days ago
yakk added startup of mbm with actvivated emu_uart, feature.. needed to be used with …
4
1 month ago
yakk removed activation of uart over emu, added reset of some peripherals
2
1 month agoo
yakk some reworks for milestone 3 12
1 year agoo
dimichxp iomux: fix address computation.
1
Just out of curiosity why did they abandon the kexec kernel swap approach?
harunjo said:
Little summary about milestone bootloader crack progress..
now they dont use kexec method anymore..they use 2nd bootloader method
Click to expand...
Click to collapse
as far as i understand it fully works except the GSM modem drivers?
so the 2ndboot works, but the port itself isn't ready? that sounds very promising. if they can extract the baseband drivers from the milestone stock OS everything works? that just sounds to good to be true
i'm currently waiting for the Droid X GSM version to be hopefully announced and if the bootloader bypassed i'm sure there will be cyanogenmod for it.
keep up the good work guys!
riggnix said:
as far as i understand it fully works except the GSM modem drivers?
so the 2ndboot works, but the port itself isn't ready? that sounds very promising. if they can extract the baseband drivers from the milestone stock OS everything works? that just sounds to good to be true
i'm currently waiting for the Droid X GSM version to be hopefully announced and if the bootloader bypassed i'm sure there will be cyanogenmod for it.
keep up the good work guys!
Click to expand...
Click to collapse
im also waiting for the GSM version to be announced. What do you make of the chances we'll hear about it (if it exists) by the next month or two?
SupremeBeaver said:
im also waiting for the GSM version to be announced. What do you make of the chances we'll hear about it (if it exists) by the next month or two?
Click to expand...
Click to collapse
i don't know... i somehow think it could be released when froyo with motoblur is ready. if we're lucky it could be as soon as august...
i also can compare to the droid and the milestone.
Droid launched on Nov. 6th,
Milestone launched on Dec. 10th.
So after Droid X being launched at Jul. 17th, maybe we'll get the Milestone X or Shadow or whatever at the end of july?
I remember them saying at the droid x launch event that they were only having a US version of this phone. Im not sure if this is correct or not.
Sent from my DROIDX using Tapatalk
hijackerjack said:
I remember them saying at the droid x launch event that they were only having a US version of this phone. Im not sure if this is correct or not.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
They said that the Droid X is a Verizon only phone. After asking if there will be a modified version like to Milestone was for Droid, the said "we can not command on unannounced products."
Same as when Droid launched. I think it's very likely that there will be a GSM version of Droid X, Motorola Milestone X or Motorola Shadow (like this one better )
We'll just have to wait and see.
riggnix said:
They said that the Droid X is a Verizon only phone. After asking if there will be a modified version like to Milestone was for Droid, the said "we can not command on unannounced products."
Same as when Droid launched. I think it's very likely that there will be a GSM version of Droid X, Motorola Milestone X or Motorola Shadow (like this one better )
We'll just have to wait and see.
Click to expand...
Click to collapse
i've been waiting for the perfect android phone since last december. i dont think i can take much more of it lol
Related
hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome
strazicic said:
hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome
Click to expand...
Click to collapse
No. Neither http://forum.xda-developers.com/member.php?u=3081699, nor http://forum.xda-developers.com/member.php?u=5019846 have this device. And there are no other developers with GT8.9.
DemonGloom said:
No. Neither http://forum.xda-developers.com/member.php?u=3081699, nor http://forum.xda-developers.com/member.php?u=5019846 have this device. And there are no other developers with GT8.9.
Click to expand...
Click to collapse
As you should remember, Arlic was the only dev of p7320 but unfortunately he disapeared suddenly...
Anyway, I am still satisfied on his rom:
http://forum.xda-developers.com/showthread.php?t=1923371
btw. there are some November's releases of stock roms at sammobile.
It is still 4.0.4 but I wonder if it comtain any improvements over previous builds?
Is your 7320 on Tegra or some diffrent SoC? I cant find reliable info...
pax0r said:
Is your 7320 on Tegra or some diffrent SoC? I cant find reliable info...
Click to expand...
Click to collapse
p7320 - SoC Qualcomm (2x1.5 Ghz, Adreno 220)
p7300/p7310 - Tegra 2
strazicic said:
hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome
Click to expand...
Click to collapse
I have just made a new kernel, but it is based on ICS.
You can get it here:
Downloads:
https://sourceforge.net/projects/kernel-p7320t-ics/files/
Source:
https://github.com/CL0SeY/kernel_P7320T_ICS
The features so far are:
Interactive CPU governor available for selection (was left out of the stock kernel for some reason). If you want to enable this governer you will need to firstly get ROOT for the tablet, and then install some app to control it, e.g. Voltage Control. If you enable this, it should give you a more responsive tablet, compared to using the default ondemand governer.
Max CPU frequency "UNICPU" bumped to 1512MHz from 1242MHz. This is the maximum frequency that you will see the tablet sitting on at times. If you are concerned about battery usage you can tweak this the maximum frequency value down using using Voltage Control or other apps.
USB charging and notification, as per glitschi667 / pershoot's patch, which was previously in a honeycomb custom kernel: http://forum.xda-developers.com/showthread.php?t=1569122 . The tablet will show as charging when plugged into a PC with enough power, whereas previously you would see the red X over the battery icon.
Wow!
Do yoy think it will work with Arlic's ROM (I am still on)?
Does it actually change charging method or just change the visualisation of the status (i.e X replaced by powering)?
Many, many thanks !!!,
I hope it is just the beginning of your magic here...
janla said:
Wow!
Do yoy think it will work with Arlic's ROM (I am still on)?
Does it actually change charging method or just change the visualisation of the status (i.e X replaced by powering)?
Many, many thanks !!!,
I hope it is just the beginning of your magic here...
Click to expand...
Click to collapse
Not too sure if it will work with Arlic's ROM. You could give it a go at your own risk, if you were keen.
The USB charging is more than just a display thing, it should work the same as glitschi667 / pershoot's one. I didn't want to advertise the charging capabilities too much without trying it myself but I can report now that it seems to charge fine off my laptop.
I will probably try next flashing the AOKP test build from the i957 forum as people have reported that it works, to some extent. I shall report back.
CL0SeY said:
Not too sure if it will work with Arlic's ROM. You could give it a go at your own risk, if you were keen.
The USB charging is more than just a display thing, it should work the same as glitschi667 / pershoot's one. I didn't want to advertise the charging capabilities too much without trying it myself but I can report now that it seems to charge fine off my laptop.
I will probably try next flashing the AOKP test build from the i957 forum as people have reported that it works, to some extent. I shall report back.
Click to expand...
Click to collapse
I have a preliminary GT-P7320T AOKP 4.1.2 ROM working based off dan-htc-touch's http://forum.xda-developers.com/showthread.php?t=1899018
I had to change the mount point for /data inside the fstab.qcom file inside the boot.img. It has to be
/dev/block/mmcblk0p28
and NOT
/dev/block/mmcblk0p26
I will hopefully report back soon. If this turns out to be all the "migration" that we need to use ROMs from the SGH-i957, it's looking good. Beware though that while they have a few devs working on ROMs it isn't extremely active over there either (http://forum.xda-developers.com/galaxy-tab-8-9/i957-development)
CL0SeY said:
I have a preliminary GT-P7320T AOKP 4.1.2 ROM working based off dan-htc-touch's http://forum.xda-developers.com/showthread.php?t=1899018
I had to change the mount point for /data inside the fstab.qcom file inside the boot.img. It has to be
/dev/block/mmcblk0p28
and NOT
/dev/block/mmcblk0p26
I will hopefully report back soon. If this turns out to be all the "migration" that we need to use ROMs from the SGH-i957, it's looking good. Beware though that while they have a few devs working on ROMs it isn't extremely active over there either (http://forum.xda-developers.com/galaxy-tab-8-9/i957-development)
Click to expand...
Click to collapse
OK, so for the game people here that want to try this out... ensure you have a stock image from sammobile ready to plonk back on your device if you're unhappy with it...
Also once I get enough posts up I might be able to make a thread in the appropriate forum
ROM (flashable CM zip): aokp_p7320t_DannoRom_Nov-03-12.CL0SeY.20131124.zip (https://drive.google.com/file/d/0B48JIYNc4wvsT2txZS16WGV0MUE/edit?usp=sharing)
GAPPS required: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Procedure:
(This has only been tested moving from a STOCK ICS ROM. Unsure if it will work for Arlic's ROM. If it all goes wrong try from a stock ICS ROM.)
Ensure you have a CWM recovery installed, see http://forum.xda-developers.com/showthread.php?t=1569122
* Copy the zips to your tablet
* Reboot into recovery
* WIPE data
* Install aokp_p7320t_DannoRom_Nov-03-12.CL0SeY.20131124.zip
* Install gapps-jb-20121011-signed.zip
* Reboot and enjoy!
Known working:
* Display
* 3G/4G/LTE
* Wifi
* Sound (headphones, speakers)
Known issues:
* Google play store seems to lose its network connection after a while. This seems to be a common problem amongst other ROMs.
* Plenty that we don't know about yet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CL0SeY said:
OK, so for the game people here that want to try this out... ensure you have a stock image from sammobile ready to plonk back on your device if you're unhappy with it...
Also once I get enough posts up I might be able to make a thread in the appropriate forum
ROM (flashable CM zip): aokp_p7520t_DannoRom_Nov-03-12.CL0SeY.20131124.zip
Click to expand...
Click to collapse
Great work!
I am going to give it a try next weekend or so.
Need to be sure no reverting problems will be while downgdading,
Definitely you should start new tread.
There is a typo in the filename of the rom?
should be p7320 instead p7520.
janla said:
Great work!
I am going to give it a try next weekend or so.
Need to be sure no reverting problems will be while downgdading,
Click to expand...
Click to collapse
Do you mean about going back to stock after trying it out? I have tried it myself going back to the sammobile OTA image fine.
janla said:
There is a typo in the filename of the rom?
should be p7320 instead p7520.
Click to expand...
Click to collapse
Yes! Thanks for picking that up... I was making the ZIP in a bit of a hurry It's definitely a typo.
---------- Post added at 05:26 PM ---------- Previous post was at 05:19 PM ----------
CL0SeY said:
Yes! Thanks for picking that up... I was making the ZIP in a bit of a hurry It's definitely a typo.
Click to expand...
Click to collapse
And the file is now named correctly
I have also succeeded in booting this ROM (CM10/JB 4.1) by using the same minor modification, but haven't uploaded my version for p7320 yet:
http://forum.xda-developers.com/showthread.php?t=1867579
It seems to be a smoother build than the AOKP one. If anyone wants me to upload it please let me know.
Also, if techy people are interested, I can make up a short guide for making a P7320 ROM out of a SGH-i957 ROM. This might be better for the "long term evolution" (pun intended ) of the tablet. But let me know if there is demand for it.
CL0SeY said:
I have also succeeded in booting this ROM (CM10/JB 4.1) by using the same minor modification, but haven't uploaded my version for p7320 yet:
http://forum.xda-developers.com/showthread.php?t=1867579
It seems to be a smoother build than the AOKP one. If anyone wants me to upload it please let me know.
Also, if techy people are interested, I can make up a short guide for making a P7320 ROM out of a SGH-i957 ROM. This might be better for the "long term evolution" (pun intended ) of the tablet. But let me know if there is demand for it.
Click to expand...
Click to collapse
OK guys, here's a nice little nugget for the weekend.
I've followed the instructions for making a CM10 ROM for the i957 above, and simply changed the mount point and have it working on the P7320.
The ROM (cm-10-20131130-UNOFFICIAL-p7320.zip) should appear in this folder as soon: https://drive.google.com/folderview?id=0B48JIYNc4wvscVpIZkRKZWd4RmM&usp=sharing
I've tested wifi, 4g, and that is about it. Once again flash at your own risk yada yada yada...
MASSIVE thanks to @nrvate for the guide! I would like to see if we can do something potentially with the upgrade scripts to make them generic. between the p7320 and i957. I suspect this ROM will work fine on the i957 with the reverse fix (ie. make it use mm block 26 instead of 28).
Also I will make a proper thread for this work soon enough...
thanks a lot for participating CL0SeY
It is great that we are moving somewhere ...
I have wish to start working on cooking but building house and 2 little children are taking all of my time (with full right
Where do people think the p7320 dev stuff should go? The I957 is sui similar, but I think people will find it easier in the other development section?
CL0SeY said:
Where do people think the p7320 dev stuff should go? The I957 is sui similar, but I think people will find it easier in the other development section?
Click to expand...
Click to collapse
I think that the "Galaxy Tab 8.9 Android Development" is the right place.
Oh, btw... I installed the CM10 to my P7320 and currently testing everything...
Issues :
Camera does not work. Camera app starts, but there's no image.
_kankea said:
I think that the "Galaxy Tab 8.9 Android Development" is the right place.
Oh, btw... I installed the CM10 to my P7320 and currently testing everything...
Issues :
Camera does not work. Camera app starts, but there's no image.
Click to expand...
Click to collapse
Same here, thanks for giving it a go and the feedback . Also, the auto brightness seems to be very unpredictable, I think it's something wrong with the values coming back from the sensor.
I've been bashing my head against a wall trying to get us up to at least cm10.1 without too much luck so far. Compiling is quite a slow process even on an SSD, so it can take a while between fixing build errors.
_kankea said:
Issues :
Camera does not work. Camera app starts, but there's no image.
Click to expand...
Click to collapse
There is a patch for the camera in the i957 thread: http://forum.xda-developers.com/showpost.php?p=31382526&postcount=47
I've downloaded it and applied it to my p7320 and it works fine.
I will incorporate it into my next update.
Other things I've noticed:
. The boot animation sometimes displays, sometimes doesn't
. Applications that want to write to USB storage seem to fail
CL0SeY said:
There is a patch for the camera in the i957 thread: http://forum.xda-developers.com/showpost.php?p=31382526&postcount=47
I've downloaded it and applied it to my p7320 and it works fine.
I will incorporate it into my next update.
Other things I've noticed:
. The boot animation sometimes displays, sometimes doesn't
. Applications that want to write to USB storage seem to fail
Click to expand...
Click to collapse
Yeah, camera works now \o/
I read from the i957-thread that the boot animation problem is a known issue...
The vibration seems to be a bit powerless...
But still, I have waited for ages that anything newer than ICS appears for this device. Great job, CL0SeY! :good:
EDIT:
Mobile hotspot function (tethering) does not seem to work...
So some kernel features through q&a
Does this kernel:
1. Play go fetch? No
2. Has this superduper ***No!
3. So this is like stock kernel but better? Yes, as is more up2date
4. Can it offer me better battery life? It might can yes
5. Can it offer me better performance too? Sure!
6. Can it play games that stock kernel cant? Performance wise they should run better
7. Can i quote this #1 post? No! you can't and you shouldn’t
8. Can i flash it on x,y,z rom? See next line:
For cm11 and compatibles
9.How i flash this? See next line:
As usual flash in recovery
Look at this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Source
Powered by loki flashing script.
Changelog for Rel4
Can you tell us what this Kernel does?
Gamma control?
Under volt?
....
Sent from my SM-N900W8 using Tapatalk
Its just a plain kernel simply updated, wip of course
Sent from my LG-P880 using Tapatalk
Didn't work for me on CM11 1/19, wiped cache and dalvik, flashed kernel then wiped dalvik and cache. Stuck on boot screen and cannot access recovery via power buttons.
Secure booting error
Cause: boot certification verify
You should be able to enter recovery as this only flashes the kernel.
Sent from my LG-P880 using Tapatalk
dont worry about the boot cert error, i already have loki-doki setup ( and a few useless kernel replacement tools) ported if need be/uploaded ( ill get it up after compiling pac), or @Demetris can lokify the boot.img if he wants
Demetris said:
Its just a plain kernel simply updated, wip of course
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Newb question. If the kernel had no added features what is different from stock kernel
Sent from my LG-V500 using Tapatalk
Canadoc said:
Newb question. If the kernel had no added features what is different from stock kernel
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
to test and eventually port the V510 (GPe Version of the LG G Pad, and probably the better kernel to base on going to kk and beyond) kernel to the v500 so that the Gpe Rom can work fully, Demetris from what i have been see might not have the tablet or the V500 version, so he needs testers to get back at him whether it works or not.
EDIT: @ikenvape if you want to give it another shot flash the zip below, it automatically lokifies and reflashes the boot.img so that you can get passed the error, ill think about setting up a thread on this much later...
Warning though, do not flash it on anything else, as there are no checks whether its a V500 or another device and can brick any other non lokifiable device
Demetris said:
You should be able to enter recovery as this only flashes the kernel.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Oh man what a ride. Yeah, couldnt get into recovery or reset, the boot error kept popping before i could hit the power button to start the operation. Used lg tools, procedure failed, then ran out of battery on the 2nd go. From there getting into download mode was touch and go. Finally got some juice for another run and was sucessfull according to the pc. The gpad was bootlooping the animation so then I retried manual reset but kept getting 'device needs to be charged more" by this time she was on charge for about an hour. Finally got manual reset to go through and voila. Lost root but not the pad.
Maybe it was a bad flash or d/l which i hope it was, but all in all, it was an entertaining night. Thanks for grabbing this and its definitely progress on the gpe road. :good:
---------- Post added at 03:00 AM ---------- Previous post was at 02:58 AM ----------
darkassain said:
to test and eventually port the V510 (GPe Version of the LG G Pad, and probably the better kernel to base on going to kk and beyond) kernel to the v500 so that the Gpe Rom can work fully, Demetris from what i have been see might not have the tablet or the V500 version, so he needs testers to get back at him whether it works or not.
EDIT: @ikenvape if you want to give it another shot flash the zip below, it automatically lokifies and reflashes the boot.img so that you can get passed the error, ill think about setting up a thread on this much later...
Warning though, do not flash it on anything else, as there are no checks whether its a V500 or another device and can brick any other non lokifiable device
Click to expand...
Click to collapse
Hey thanks man. Ill hold on to it for when i re-root in a bit.
no testers ?
I'am curious to know if it's working or not ( i can't test it for now since i have a week of exams... sure i will test at the end of the week)
Ok guys. i think you must be kidding me.
You scream and yell you want the Gpe Source code fully working on v500 and i see no reports here and only 3 downloads.
Didn’t i ask my self why bother but i do now.
This stays close to public until further notice.
I hope you are happy.
Edit Since the previous post am been getting a lot of pm's and interest on this seems healthy.
Downloads have increased and i know lokified script needs fixing as it doesn’t work now.
So ....
Lets continue the gpe kernel shall we?
Thread re-opened.
Thanks to all xda users for their reports and support on this, i hope for the best :fingers-crossed:
Demetris said:
Ok guys. i think you must be kidding me.
You scream and yell you want the Gpe Source code fully working on v500 and i see no reports here and only 3 downloads.
Didn’t i ask my self why bother but i do now.
This stays close to public until further notice.
I hope you are happy.
Edit Since the previous post am been getting a lot of pm's and interest on this seems healthy.
Downloads have increased and i know lokified script needs fixing as it doesn’t work now.
So ....
Lets continue the gpe kernel shall we?
Thread re-opened.
Thanks to all xda users for their reports and support on this, i hope for the best :fingers-crossed:
Click to expand...
Click to collapse
tried flashing the kernel in the first post with no luck, doesn't even flash so i can't even loki doki it
I'll fix it asap currently busy with slim
Sent from my LG-P880 using Tapatalk
Demetris said:
I'll fix it asap currently busy with slim
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
no rush man just letting you know
Demetris said:
Ok guys. i think you must be kidding me.
You scream and yell you want the Gpe Source code fully working on v500 and i see no reports here and only 3 downloads.
Didn’t i ask my self why bother but i do now.
This stays close to public until further notice.
I hope you are happy.
Edit Since the previous post am been getting a lot of pm's and interest on this seems healthy.
Downloads have increased and i know lokified script needs fixing as it doesn’t work now.
So ....
Lets continue the gpe kernel shall we?
Thread re-opened.
Thanks to all xda users for their reports and support on this, i hope for the best :fingers-crossed:
Click to expand...
Click to collapse
since i you closed this thread without being able to voice my thoughts, i honestly believe that you pulled the plug a little too early, not only are we a small bunch of users compared to nexus and other tablet makers counterparts, but its it feels like there was no marketing at all, just word of mouth and a few publications pushing reviews (which i still dont understand how only one review noticed the few screen issues most have noticed),
sorry for OT, back on topic since i have the device ill take a look at your zip and see if ill be able to fix it...
EDIT: Took a quick look at the script and it seems the loki tools and script arent in the zip, simple fix which im uploading now
EDIT2: @thoughtlesskyle try it now...
darkassain said:
since i you closed this thread without being able to voice my thoughts, i honestly believe that you pulled the plug a little too early, not only are we a small bunch of users compared to nexus and other tablet makers counterparts, but its it feels like there was no marketing at all, just word of mouth and a few publications pushing reviews (which i still dont understand how only one review noticed the few screen issues most have noticed),
sorry for OT, back on topic since i have the device ill take a look at your zip and see if ill be able to fix it...
EDIT: Took a quick look at the script and it seems the loki tools and script arent in the zip, simple fix which im uploading now
EDIT2: @thoughtlesskyle try it now...
Click to expand...
Click to collapse
still getting a binary error
thoughtlesskyle said:
still getting a binary error
Click to expand...
Click to collapse
whoops didnt upload the right edited one...
one last try
darkassain said:
whoops didnt upload the right edited one...
one last try
Click to expand...
Click to collapse
Giving it a go now, trying the Gpe Rom hopefully this fixes it (I got a feeling there is little chance)
Sent from my HTCONE using Tapatalk
thoughtlesskyle said:
Giving it a go now, trying the Gpe Rom hopefully this fixes it (I got a feeling there is little chance)
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
i believe some of ricardos patches need to be reverted before that, this is mainly a base to build off for @Demetris
Hi everyone,
So here is a little tool I used firstly for myself because
I was tired of having to type the required command to flash my recovery from a recovery to another.
This tool was originaly made for XT925, but as asked I produced a MB886 version (and a full version too).
Using it elsewhere might produce undesired side-effects.
v1.4 for XT925 and MB886 - 46.5 Mo
v1.4 for XT925 only - 16.7 Mo
v1.4 for MB886 only - 30.3 Mo
To use it, just extract it wherever you want and launch InstallRecovery.bat
Then follow the instructions
Currently supports :
XT925
Philz_touch_6.00.8 for XT925
Recovery_ClockWork-6.0.4.4 for XT925
TWRP 2.6.0.0 for XT925
TWRP 2.2 for XT925
MB886
Philz_touch_6.12.8 for MB886
Recovery_ClockWork-6.0.4.4 for MB886
QR Code for MB886 version (Atrix HD) :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If only this came out before I got my recovery! Haha. good release either way, it will be useful for other people.
Sent from my MB886 using Tapatalk
I thought we only had TWRP on XT926 and the touch points were way off for us? Either way, anyone tried the XT925 TWRP?
Sent from my MB886 using Tapatalk
penser said:
I thought we only had TWRP on XT926 and the touch points were way off for us? Either way, anyone tried the XT925 TWRP?
Sent from my MB886 using Tapatalk
Click to expand...
Click to collapse
Same problem
Thanks Hybris
penser said:
I thought we only had TWRP on XT926 and the touch points were way off for us? Either way, anyone tried the XT925 TWRP?
Sent from my MB886 using Tapatalk
Click to expand...
Click to collapse
TecknoFreak said:
Same problem
Thanks Hybris
Click to expand...
Click to collapse
Well I use TWRP nearly everyday on XT925, the 2.6.0.0 works perfectly. I just have some problems with rights which I fix by using this command :
Code:
chmod -R 777 /data/media
with adb shell in su or with the shell integrated in TWRP
Hybris95 said:
Well I use TWRP nearly everyday on XT925, the 2.6.0.0 works perfectly. I just have some problems with rights which I fix by using this command :
Code:
chmod -R 777 /data/media
with adb shell in su or with the shell integrated in TWRP
Click to expand...
Click to collapse
We have a different touchscreen and neither TWRP or Aroma installers work with the Atrix HD. The problem is our touchpoints are recognized down and to the left (iirc) of where we actually press.
skeevydude said:
We have a different touchscreen and neither TWRP or Aroma installers work with the Atrix HD. The problem is our touchpoints are recognized down and to the left (iirc) of where we actually press.
Click to expand...
Click to collapse
Actually any Aroma installers work just fine for me, not sure why they haven't for you.
penser said:
Actually any Aroma installers work just fine for me, not sure why they haven't for you.
Click to expand...
Click to collapse
They never have for me, always had the exact same touch issues as TWRP, at least with the first Philz CWM release and earlier. Haven't bothered testing since then.
The aroma file manager for Philz recovery works perfect. Now, any other aroma zip installer is a no for my atrix
skeevydude said:
We have a different touchscreen and neither TWRP or Aroma installers work with the Atrix HD. The problem is our touchpoints are recognized down and to the left (iirc) of where we actually press.
Click to expand...
Click to collapse
Can you confirm that you have the same problem with the versions I gave in my installer ?
I got em from a specific thread for Atrix so maybe it's bugfixed.
skeevydude said:
They never have for me, always had the exact same touch issues as TWRP, at least with the first Philz CWM release and earlier. Haven't bothered testing since then.
Click to expand...
Click to collapse
TecknoFreak said:
The aroma file manager for Philz recovery works perfect. Now, any other aroma zip installer is a no for my atrix
Click to expand...
Click to collapse
I have Philz working just fine on my AHD, but last I tried to install Aroma the touch points were also way off. Don't know the exact version it was, but I believe I was following the directions here: http://forum.xda-developers.com/showthread.php?t=2201860
So I gave up on it.
Isn't this just like Mythtools? Looking at your script, agreed it is different, but the basic function is the same between yours and theirs.
Sent from my MB886 using xda app-developers app
palmbeach05 said:
Isn't this just like Mythtools? Looking at your script, agreed it is different, but the basic function is the same between yours and theirs.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Im not really aware of existing tools Im pretty new around Android community since I never had a smartphone before that
This is only a tool I made for myself and distributed for you guys, no real intention on making a great tool or whatever, just sharing ^^
Edit : I searched a bit about Mythtools, they only support Atrix or have they made any other device's tool like I do ?
You good no matter what but now that your source is out compare it and credit who ever you think coded first.
---------- Post added at 10:37 PM ---------- Previous post was at 10:36 PM ----------
The end fact is that you put together a tool not done and is not just a straight copy cat.
TecknoFreak said:
You good no matter what but now that your source is out compare it and credit who ever you think coded first.
---------- Post added at 10:37 PM ---------- Previous post was at 10:36 PM ----------
The end fact is that you put together a tool not done and is not just a straight copy cat.
Click to expand...
Click to collapse
I've looked at the code of both and this is unique. There's only so many ways to call adb and fastboot with a script....I'd probably write something similar starting from nothing.
This reminds me of Microsoft suing ReactOS over some driver. The were using the exact same source code as Microsoft, but it turned out that ReactOS just happened to have developed the same code because that's what worked, not from stealing or reverse engineering.
Hell, this might be Hybris's first dive into either scripting or trying automating the flashing process....one of the reasons I suggest learning the manual way is because if this, Myth, or who/whatever happens to screw up and release something bad (not accusing them of anything, just examples that are common in our forums) and you used that tool, it's on you if you get bricked, not the tool maker. Fact is,ya'll's the ones downloading a tool because you're too lazy to learn it on your own (not directed at TecknoFreak, just noobs).
palmbeach05 said:
Isn't this just like Mythtools? Looking at your script, agreed it is different, but the basic function is the same between yours and theirs.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Sometimes, people may have the same idea, the differences are time and how they process it idea to a real thing
I think maybe Hybris and our tools has the same function at flashing recovery but both are not the same exactly.
However, in my opinion, more tools will benefit more for users
Hybris95
Im not really aware of existing tools Im pretty new around Android community since I never had a smartphone before that
This is only a tool I made for myself and distributed for you guys, no real intention on making a great tool or whatever, just sharing ^^
Edit : I searched a bit about Mythtools, they only support Atrix or have they made any other device's tool like I do ?
Click to expand...
Click to collapse
Currently, I have only Atrix now. That's why I only made tools for it. In the past, I also modded for samsung devices but it's different from motorola so there is no Myth Tools for them - Only Myth Roms
Btw, your tools is really good and I expect to see other ones from you.
BR,
DK
TecknoFreak said:
You good no matter what but now that your source is out compare it and credit who ever you think coded first.
---------- Post added at 10:37 PM ---------- Previous post was at 10:36 PM ----------
The end fact is that you put together a tool not done and is not just a straight copy cat.
Click to expand...
Click to collapse
Mmh after a while thinking....let's credit....mmmh...myself ? ^^"
What do you mean by a "a tool not done" ?
skeevydude said:
I've looked at the code of both and this is unique. There's only so many ways to call adb and fastboot with a script....I'd probably write something similar starting from nothing.
This reminds me of Microsoft suing ReactOS over some driver. The were using the exact same source code as Microsoft, but it turned out that ReactOS just happened to have developed the same code because that's what worked, not from stealing or reverse engineering.
Hell, this might be Hybris's first dive into either scripting or trying automating the flashing process....one of the reasons I suggest learning the manual way is because if this, Myth, or who/whatever happens to screw up and release something bad (not accusing them of anything, just examples that are common in our forums) and you used that tool, it's on you if you get bricked, not the tool maker. Fact is,ya'll's the ones downloading a tool because you're too lazy to learn it on your own (not directed at TecknoFreak, just noobs).
Click to expand...
Click to collapse
Well this is not my first scripting in batch but my first attempt (and probably last ^^) at automating the flashing process.
I'm not trying to make the perfect and flawless tool, just a share of my work.
If you don't trust it, analyse it or don't use it.
By the way, I did NOT tested the Atrix part since I don't own an Atrix myself.
This tool did not passed any unit-test so it "may" bug in some cases (like for example n a locked device)
devilsking said:
Sometimes, people may have the same idea, the differences are time and how they process it idea to a real thing
I think maybe Hybris and our tools has the same function at flashing recovery but both are not the same exactly.
However, in my opinion, more tools will benefit more for users
Click to expand...
Click to collapse
I can only agree on this, our tools just shows it, we are allowing people to flash multiple tools on their device, it's only a matter of choices and functionalities
devilsking said:
Currently, I have only Atrix now. That's why I only made tools for it. In the past, I also modded for samsung devices but it's different from motorola so there is no Myth Tools for them - Only Myth Roms
Btw, your tools is really good and I expect to see other ones from you.
BR,
DK
Click to expand...
Click to collapse
Well maybe some other tools who knows, not me at least
I think the next things I will get to try out developping will be recovery imgs itselves that sounds pretty fun and interesting ^^
(For example : allowing adb from being executed from a recovery (even a few cmds) ? or allowing MTP service withing a recovery ?)
Hybris95 said:
Mmh after a while thinking....let's credit....mmmh...myself ? ^^"
What do you mean by a "a tool not done" ?
Click to expand...
Click to collapse
Hahaha i ment no one came out with such a tool. Just like it bro.
Good job and ty
@Hybris95
It might not have sounded like it, but I wasn't talking bad about you or this...
I was just saying if someone uses a tool to do something without bothering to learn how something is done, it's that persons fault for taking the easy way if it doesn't work, even if the tool is at fault -- the reason -- most bad things thst can occur with tools like this are easy to fix, but artard here only uses tools and never adb or fastboot, so if something goes wrong they don't know what to do. There's also cases where X worked for me, I release, and TecknoFreak uses it and is forced to fastboot to stock...if noobXyZ used it, I'd be dealing with "you broke my phone" and maybe having to play tech support.
Mythtools have left inexperienced users with fixable bricks in the past. Was it user error, the tool, God, a bad usb cable, the driver??? Who knows, but derp follows, and then we get to answer help, help, help posts (see video in one of my stickied guides...probably explains this better than me).
EDIT:
And I did analyze this. I do it to every automated tool I use. That's why I posted that you didn't use anyone else's work when making this. A quick glance at it and that was obvious.
Well if anyone has issues with my tool i'd be glad to help if i can, but as i said i cant unit test everything especially since fastboot is very limited compared to adb and since i cant buy every devices
Envoyé de mon XT925 en utilisant Tapatalk
Credits:
Original version created in the summer of 2011. Thanks to birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch!
Special thanks to tiny4579 and ghul21 for testing on the OnePlus One!
Thanks to SDX
Requires:
Unlocked bootloader (shouldn't be a concern here!) and root access!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY select Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into a kernel /sbin directory, included in custom ROMs, etc).
Description:
This android application, FlashImageGUI, is a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: OnePlus One, HTC One M8 (GSM), Moto G, Sprint Galaxy S4, International HTC One (M7), T-Mobile HTC One (M7), Sprint HTC One (M7), HTC EVO 4G LTE, HTC One S, HTC EVO 3D CDMA and GSM, HTC One XL, HTC Droid DNA, HTC Amaze, HTC Vivid/Holiday, HTC EVO 4G, HTC EVO Shift, Google Nexus 5, Google Nexus 4, Google Nexus 10, Google Nexus 7, Samsung Google Galaxy Nexus, Nexus S/Nexus S 4G & LG Optimus
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
Let me know if there are any issues. Feel free to post the encountered issue and a link to the exact file that was flashed. Thanks for the support!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No.
Q: Can I flash nandroid kernel backups?
A: Yes. Rename the specific image to boot.img and select from inside of Flash Image GUI. **Make sure to also load the associated modules or WiFi might stop working!
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
Users Guide for flashing ONLY a Kernel (zip file):
1) Ensure the bootloader is unlocked and root access is properly setup
2) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
3) Download kernel zip file to /sdcard.
4) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
5) Flash Image GUI will validate that the kernel zip file contains the minimum required files
6) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
7) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel itself or the ramdisk packaged in the kernel is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot (or directly into the custom recovery) and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.
Completely surprised your thanks meter is not higher than what it is for the length of time you been helping out with your apps up in here. If I remember right you go way back to the winmo days right?
Thx for your app and allow me to be the first to thank you in the 1+ section :good:
playya said:
Completely surprised your thanks meter is not higher than what it is for the length of time you been helping out with your apps up in here. If I remember right you go way back to the winmo days right?
Thx for your app and allow me to be the first to thank you in the 1+ section :good:
Click to expand...
Click to collapse
I have been around a long while, and spent more time on here before the thanks meter was added (Dec 2010).
I appreciate the support and feel free to provide feedback as I'm always interested in improving!
Quick question, how does this app differ from one like Flashify? Is it another alternative?
Don't get me wrong, I'm all for lots of new development and different alternatives, just trying to understand if this app provides something different (or at least does it better) than some other similar apps.
Thanks!
pinoymutt said:
Quick question, how does this app differ from one like Flashify? Is it another alternative?
Don't get me wrong, I'm all for lots of new development and different alternatives, just trying to understand if this app provides something different (or at least does it better) than some other similar apps.
Thanks!
Click to expand...
Click to collapse
I can't speak to Flashify, other than it didn't exist when I created Flash Image GUI ~3 years ago. I'm also unsure about their business model, whether they're free and charge for usage or whether they charge for the app.
Either way, I host a free copy of Flash Image GUI for XDA users and do my best to monitor this thread for any issues, concerns, or bugs, as I've done for around 30 devices over the last three years!
Thanks for your support!
Nice to see you around here @joeykrim! I still have my Moment around here somewhere running something crazy from SDX.
Hi joeykrim
Nice to see you start a thread in here
Some time ago i post you an email to support Oneplus One and we made some tests
thx for the app and finaly full support for OPO on XDA. Glad it finally work for "all" of my devices
One more time THX for amazing app
Regards
Marcin :highfive:
ghul21 said:
Hi joeykrim
Nice to see you start a thread in here
Some time ago i post you an email to support Oneplus One and we made some tests
thx for the app and finaly full support for OPO on XDA. Glad it finally work for "all" of my devices
One more time THX for amazing app
Regards
Marcin :highfive:
Click to expand...
Click to collapse
Yes, I appreciated you reaching out and requesting support, plus spending time testing as I added support. I've added your XDA name to the credits at the top. Thanks again for your help!
Thanx for adding support for opo, but could you make recognize the "any kernel" zip files as it does not contain img's.several kernel dev's are using this method nowadays,so their kernel is compatible across all rom's..
zodiaxe66 said:
Thanx for adding support for opo, but could you make recognize the "any kernel" zip files as it does not contain img's.several kernel dev's are using this method nowadays,so their kernel is compatible across all rom's..
Click to expand...
Click to collapse
I do support the method on devices where the kernel devs follow common and standard usage of the anykernel method, but didn't see this on the OPO a few weeks back.
Can you provide links to the specific kernels on the OPO that are using this method? When I checked a few weeks back, there was only one and they were using an unusual variation of the anykernel method that I hadn't seen on any other device before.
Thanks for your support!
joeykrim said:
I do support the method on devices where the kernel devs follow common and standard usage of the anykernel method, but didn't see this on the OPO a few weeks back.
Can you provide links to the specific kernels on the OPO that are using this method? When I checked a few weeks back, there was only one and they were using an unusual variation of the anykernel method that I hadn't seen on any other device before.
Thanks for your support!
Click to expand...
Click to collapse
Here you go and thanx
Ups my link in gone
Posting it later when i'm home..it's AK kerne by AK in original Android dev
http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
EDIT: heres a screenshot of chosen kernel I tried to flash. Your app doesn't recognize the zImage..
Device not supported?
zodiaxe66 said:
Here you go and thanx
Ups my link in gone
Posting it later when i'm home..it's AK kerne by AK in original Android dev
http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
EDIT: heres a screenshot of chosen kernel I tried to flash. Your app doesn't recognize the zImage..
Click to expand...
Click to collapse
The link is helpful and that was the one kernel using the "AnyKernel" method but in a less common manner that I'm hesitant about adding support for. I appreciate the request and can investigate it further but at this point, that one kernel likely won't be a high priority unless many other people request it, mostly due to the less common manner it uses to load. I view there be additional risk to adding less common loading methods in that I don't want to damage any devices using less proven methods. Given that I don't own the device myself, I'm also less likely to ask testers to risk using a less common loading method to test support.
lqdcat said:
Device not supported?
Click to expand...
Click to collapse
The screenshot is very helpful and ironically shows that this is the kernel, quoted above, that I'm hesitant to add flashing support to as it uses less common methods of loading. It seems that either the kernel or the ROM changes how the device identifies itself and breaks compatibility with Flash Image GUI. Which ROM are you using?
While you're still using that kernel and ROM combination, can you share the output from the following adb shell command? adb shell getprop ro.product.device
joeykrim said:
The link is helpful and that was the one kernel using the "AnyKernel" method but in a less common manner that I'm hesitant about adding support for. I appreciate the request and can investigate it further but at this point, that one kernel likely won't be a high priority unless many other people request it, mostly due to the less common manner it uses to load. I view there be additional risk to adding less common loading methods in that I don't want to damage any devices using less proven methods. Given that I don't own the device myself, I'm also less likely to ask testers to risk using a less common loading method to test support.
The screenshot is very helpful and ironically shows that this is the kernel, quoted above, that I'm hesitant to add flashing support to as it uses less common methods of loading. It seems that either the kernel or the ROM changes how the device identifies itself and breaks compatibility with Flash Image GUI. Which ROM are you using?
While you're still using that kernel and ROM combination, can you share the output from the following adb shell command? adb shell getprop ro.product.device
Click to expand...
Click to collapse
Okay I understand, Thanx for your response and to clear things up.
PS. I have no problem with my opo getting recognized, so apparently it's as you pointed out, only the one kernel, sadly, but there are many other ways to flash it, so no worries.. :highfive:
it took about 2 seconds to flash a new recovery.img
Excellent
Thank you very much!!
- Discontinued.
- This was only really useful for people that unlocked on firmwares older than xx.3.2.3.2.
- It should no longer be needed
If your bootloader is not unlocked OR you are running Safestrap 4.xx, please walk away now
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
Code:
[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
Hello all,
Here are some bootloader upgrade images which allow you to upgrade your system to .3.2.3.2 without flashing the full amazon stock firmware image.
The reason you might want to do this is because a few people have reported graphical glitches/black screen issues while trying to run HDX Nexus ROM.
Updating to .3.2.3.2 seems to fix the problems.
These update images will flash the bootloaders on your system.
They will NOT flash the modem firmware, /boot , /recovery or /system partitions.
*** PLEASE CHECK THE MD5 OF THESE AFTER DOWNLOADING AND BEFORE FLASHING ***
I have tested both of them Apollo and Thor respectively.
Instructions
- Copy the file to your /sdcard on your device
- Flash the file with TWRP
- Reboot
Downloads
- Discontinued.
- This was only really useful for people that unlocked on firmwares older than xx.3.2.3.2.
- It should no longer be needed
Great work mate!
Great @ggow, wanted to that for weeks
Yup, worked great for me too. Fixed occasional gallery FCs on boot which was the only issue I was experiencing with the older bootloader.
@ggow Will there be any thing available for kindle with 14.3.2.8 software?
Mr.Dumb said:
@ggow Will there be any thing available for kindle with 14.3.2.8 software?
Click to expand...
Click to collapse
In short, no. The exploit was patched in .3.2.4.
Sent from my Nexus 6 using Tapatalk
ggow said:
In short, no. The exploit was patched in .3.2.4.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Okay thanks a lot for the answer, as i have root access can i downgrade by fooling system that i have a lower build (editing build prop) and then updating the lower build.
In short ill make build prop edit to a lower version than .3.2.4 or so and then sideload update the .3.2.3 Firmware. ?
Mr.Dumb said:
Okay thanks a lot for the answer, as i have root access can i downgrade by fooling system that i have a lower build (editing build prop) and then updating the lower build.
In short ill make build prop edit to a lower version than .3.2.4 or so and then sideload update the .3.2.3 Firmware. ?
Click to expand...
Click to collapse
Err, don't think that's going to work. If it were that easy folks would be downgrading from 3.2.7/3.2.8 in droves (and certainly the devs would have supplied a tool for the masses). Best catch up by reading through the forums and learning what can and can't be done with your device given the current firmware level.
Just to let you know, the thor ZIP incorrectly mentions "apollo" after flashing. I got scared for a second.
EncryptedCurse said:
Just to let you know, the thor ZIP incorrectly mentions "apollo" after flashing. I got scared for a second.
Click to expand...
Click to collapse
Thanks for letting me know, I'll update it at the next opportunity.
Sent from my Nexus HDX 8.9 using Tapatalk
ggow said:
In short, no. The exploit was patched in .3.2.4.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Is there any rollback protection in place for 'aboot'?
If not (wishful thinking, I guess) flashing any valid
(i.e. Amazon-signed) 'emmc_appsboot.mbn' should work.
Do we know?
---------- Post added at 20:44 ---------- Previous post was at 20:40 ----------
Mr.Dumb said:
@ggow Will there be any thing available for kindle with 14.3.2.8 software?
Click to expand...
Click to collapse
Could you post the exact version of your system software (including _user_32800XXXX)?
You'll find this under Settings/Device/System Updates/Current Version...
draxie said:
Is there any rollback protection in place for 'aboot'?
If not (wishful thinking, I guess) flashing any valid
(i.e. Amazon-signed) 'emmc_appsboot.mbn' should work.
Do we know?
---------- Post added at 20:44 ---------- Previous post was at 20:40 ----------
Could you post the exact version of your system software (including _user_32800XXXX)?
You'll find this under Settings/Device/System Updates/Current Version...
Click to expand...
Click to collapse
@draxie
It is very probable that flashing an old emmc_appsboot.mbn on .3.2.8 will trigger the rollback protection. Something else that might have changed is that the DTB table layout might have changed which would make it incompatible with any installed recovery or boot image. If someone can dump the boot partition from a device running 3.2.8 I could let you know whether that is the case.
If the above is satisfiable in our favour then we would need to check whether the same RSA signature in the .3.2.8 SBL used to check the aboot image is the same as the old SBL's RSA signature. Then there might be a chance to flash an older amazon signed aboot.img.
It's a longshot.
ggow said:
@draxie
It is very probable that flashing an old emmc_appsboot.mbn on .3.2.8 will trigger the rollback protection. Something else that might have changed is that the DTB table layout might have changed which would make it incompatible with any installed recovery or boot image. If someone can dump the boot partition from a device running 3.2.8 I could let you know whether that is the case.
If the above is satisfiable in our favour then we would need to check whether the same RSA signature in the .3.2.8 SBL used to check the aboot image is the same as the old SBL's RSA signature. Then there might be a chance to flash an older amazon signed aboot.img.
It's a longshot.
Click to expand...
Click to collapse
You are, of course, right on all counts.
Nevertheless, the 3.x.y series is basically JB, with the same DT format everywhere,
but I'd also like to double check. That's why I asked for the full version string, hoping
to find the update image on Amazon's servers.
As for the SBL, which partitions are relevant?
I know for a fact that the 4.5.2 firmware (except aboot) work fine with 3.2.3.2,
as I flashed those myself... Those included tz, rpm, sbl1, and dbi/sdi.
I'd say we may have a chance; but it IS risky.
I believe this can be found in buildprop
Else contact customer care and ask them links + version strings.
They will help and that person will get a "yes" at least
Edit :
Found in build prop : 14.3.2.8_user_328003120
AmazonLeaker said:
I believe this can be found in buildprop
Else contact customer care and ask them links + version strings.
They will help and that person will get a "yes" at least
Edit :
Found in build prop : 14.3.2.8_user_328003120
Click to expand...
Click to collapse
Thanks!
Unfortunately, the OTA update with this version does not seem to be available at the usual place...
draxie said:
Thanks!
Unfortunately, the OTA update with this version does not seem to be available at the usual place...
Click to expand...
Click to collapse
Its updated to 4.5.3
draxie said:
Thanks!
Unfortunately, the OTA update with this version does not seem to be available at the usual place...
Click to expand...
Click to collapse
Hey [email protected] I'm sorry but i don't understand what do you want to point out ?
Do you mean to say that the file is not there ?
Well its not in the aws server anymore i believe, however I'd suggest you to contact customer care and inform them of this get a ticket raised (better possibility) and /or get this fixed on call itself (very thin chances of this).
Please note : there is some customer service team outsourced at pune & chennai they are very notorious and lie so please beware! (you can only identify them by their very odd names)
ggow said:
@draxie
It is very probable that flashing an old emmc_appsboot.mbn on .3.2.8 will trigger the rollback protection.
Click to expand...
Click to collapse
Actually, I have another data point here: I rolled back from 3.2.6 to 3.2.3.2
following the relatively procedure from the scripts posted here .
This involved building stock recovery from the OTA (basically the same way the shell script does).
Changing build.prop and applying the OTA straight from the /sdcard.
No real rollback protection to speak of.
I don't see why this shouldn't work on 3.2.8...
AFAICT, the recovery stuff had to be done not to trip a check in the updater-script.
Similarly, the build.prop stuff is probably needed so that the com.amazon.dcp app/library
would pick up the update.
I think I convinced myself enough that I might try flashing aboot at some point...
mayur.3.92 said:
Its updated to 4.5.3
Click to expand...
Click to collapse
AmazonLeaker said:
Hey [email protected] I'm sorry but i don't understand what do you want to point out ?
Do you mean to say that the file is not there ?
Well its not in the aws server anymore i believe, however I'd suggest you to contact customer care and inform them of this get a ticket raised (better possibility) and /or get this fixed on call itself (very thin chances of this).
Please note : there is some customer service team outsourced at pune & chennai they are very notorious and lie so please beware! (you can only identify them by their very odd names)
Click to expand...
Click to collapse
I guess what I'm wondering is whether the update image for this version
(and 1x.3.2.7) was ever publicly released, since pretty much all earlier versions
I've tried can still be downloaded from Amazon at the URL
https://kindle-fire-updates.s3.amazonaws.com/
alternatively
https://s3.amazonaws.com/kindle-fire-updates/
followed by 'update-kindle-LONG_VERSION.bin',
which kind of makes sense considering that there
_could_ be devices out there with any version...
These "milestone" versions are all still available:
1x.3.1.0_user_310079820 (first[?] root)
1x.3.2.3.2_user_323001720 (latest with RSA bug)
1x.3.2.6_user_326001820 (latest with no rollback protection?)
SO, my question is -IF you have a 1x.3.2.8- did you receive it as normal OTA,
or are these rollback-protected images distributed only to those that didn' t
want 4.x.x... I'm just speculating here, of course.
It looks like I've gotten an answer in the meantime..
Davey126 said:
Err, don't think that's going to work. If it were that easy folks would be downgrading from 3.2.7/3.2.8 in droves (and certainly the devs would have supplied a tool for the masses). Best catch up by reading through the forums and learning what can and can't be done with your device given the current firmware level.
Click to expand...
Click to collapse
Yeah, AFAIK you can only use the build.prop edit downgrade for non-bootloader change updates. While you may be able to change from 3.2.8 to 3.2.7 (if the bootloader was not updated), you still cannot roll back any further because of the "roll back bootloader" efuse that was added, which is why Amazon won't downgrade certain people below a certain version, they simply can't do it.
However, if you have 3.2.6, then you could probably use the edited prop file & just flash the complete earlier version OTA.
I am going to have to play with this a bit, because it has me curious about what changes they have made & whether I can then get the 4.5.x kernel & system partition working with the 3.2.3 bootloader.
Speaking of which.... Have any of you that have been involved with the signing tool decompiled the various bootloader versions? How much difference did you notice? I am wondering if it's just address space & vuln patches, or if it is going to be a time consuming thing to catch up & figure out what needs to be & even can be changed to offer 4.5x features alongside the 3.2.3 bootloader...
EDIT: AND... I see ggow has been working on this...