If your not running 51.1.4.1_514013920+fixed from rbox's Prerooted Stock Images thread; do not bother to load this one.
No support will be offered if your firetv screws up.
With that said, I have been running this for the past few days without issue and thought I would make it available to those that want it.
bueller-51.1.4.3_514020320-my_rooted.zip (md5sum: f54cec620785b04d1fcd5a660b9a79ff)
BBB
Going Shoeless.
realbbb said:
If your not running 51.1.4.1_514013920+fixed from rbox's Prerooted Stock Images thread; do not bother to load this one.
No support will be offered if your firetv screws up.
With that said, I have been running this for the past few days without issue and thought I would make it available to those that want it.
bueller-51.1.4.3_514020320-my_rooted.zip (md5sum: f54cec620785b04d1fcd5a660b9a79ff)
BBB
Going Shoeless.
Click to expand...
Click to collapse
What kernel is included in this?
rbox said:
What kernel is included in this?
Click to expand...
Click to collapse
The one included with your 51.1.4.1 release.
BBB
Slightly sloppy.
Thanks
Anything new at all?
jarayn said:
Thanks
Anything new at all?
Click to expand...
Click to collapse
Nothing visually different. Seems to be just bug fixes. Seems snappier, but that might just be a cache wipe or a placebo effect. [emoji6]
BBB
Something Grandiose
Installed with no problems. rboxes exposed stuff still works.. Thanks for putting this out...
Working fine for me. Thanks!
thanks you for your work.
As a note to remind myself of how to install future updates:
Firetv: system, about, network, get IP address.
Computer: command prompt, adb connect (ip address), adb push (rom.zip or the name of the rom file) /sdcard/,
To check if the amazontv is downloading rom file: WIFI, open network and sharing center, change network adapter, WIfi, status
when it is finishes transfering (eta 10-15 mins): adb reboot recovery, connect usb keyboard, install zip, /0/, /sdcard/, (rom.ziop or the name of the rom file), restart system. Done.
Great work! Thank you. I will install this tonight. Quick question: Is it a requirement to have a fully unlocked bootloader or no?
I'm partially unlocked at the moment, but will fully unlock it if necessary. Just haven't gotten around to it.
Newbie_from_NJ said:
Great work! Thank you. I will install this tonight. Quick question: Is it a requirement to have a fully unlocked bootloader or no?
I'm partially unlocked at the moment, but will fully unlock it if necessary. Just haven't gotten around to it.
Click to expand...
Click to collapse
Full unlock is not necessary. Though, I did apply the full unlock to mine.
BBB
Growing Tight.
What benefits are there to installing this over the previous pre-root version? I'm setup rather nicely and don't want to risk rocking the boat.
xm41907 said:
What benefits are there to installing this over the previous pre-root version? I'm setup rather nicely and don't want to risk rocking the boat.
Click to expand...
Click to collapse
I will hold off until there is a release that justifies the installation. There are no added benefits of this release. I was hoping Miracast from the windows PC would work. that is one big benefit for the Microsoft world.
navigates said:
I will hold off until there is a release that justifies the installation. There are no added benefits of this release. I was hoping Miracast from the windows PC would work. that is one big benefit for the Microsoft world.
Click to expand...
Click to collapse
That's what I was figuring.
Does my firetv need to be rooted to use this ROM?
death_entry said:
Does my firetv need to be rooted to use this ROM?
Click to expand...
Click to collapse
Yes, how else would you manage it to get it running on there?
does it matter which version I'm currently on before upgrading?
superkevx said:
does it matter which version I'm currently on before upgrading?
Click to expand...
Click to collapse
Read the first line in the first post....
Hi, will this work on fire tv stick? what about efuse and all that stuff from amazon blocking root?
This is not for the Fire TV Stick
Related
First time posting........ here is the International Version of latest ICS 4.0.3 RC released on Mar 26: S7-301u_V100R002C002B008
Huawei did an excellent job in tunning ICS, it is very fast, stable and incorporates some of the latest features! Here's the download link!
S7-301u_V100R002C002B008
http://www.uploadstation.com/file/GXPgCZF/S7-301u_Intl_V100R002C002B008.rar
Latest One Key root for Mediapad
http://www.uploadstation.com/file/gX69WT8/4.0_One_Key_root.rar
Flash method : Unzip the downloaded .rar file and place the "dload" folder on the root of the SDCARD, reboot and whala~~ enjoy
Note: I am not responsiblt if you somehow screw up your device!!!
Thanks, I tried this ROM. First impressions seem fast and more slick than previous ICS releases.
But got a couple of problems: Mobile data is broken, I only have wifi. Zinio app doesn't work properly. Good thing is that Amazon Kindle works, so I might just stick with this for a while.
I haven't tried the rooting yet, not sure how to go about it. Any tips?
Update: I accidentally reflashed the ROM, having left the dload folder in the SD card. To my surprise, the mobile data now works fine in 3G mode. Pity Zinio still gives me an error message, but that's probably due to the app's incompatibility with ICS.
Try to enable/disable Plane-Mode. It should work then. Here WLAN and 3G just works finde.
Well, I am not a developer so can't really help solving ur issue, but did you try to factory reset and reboot after the flash? Everything seems working fine on my deivce!!
For the root, connect the device to PC, extract the .rar file, copy the folder under C:\ and run the .bat file "TPSparkyRoot", it should run itself automatically!
Rumbi said:
Try to enable/disable Plane-Mode. It should work then. Here WLAN and 3G just works finde.
Click to expand...
Click to collapse
Thanks, it turns out that it wasn't necessary.
---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------
octpus said:
Well, I am not a developer so can't really help solving ur issue, but did you try to factory reset and reboot after the flash? Everything seems working fine on my deivce!!
For the root, connect the device to PC, extract the .rar file, copy the folder under C:\ and run the .bat file "TPSparkyRoot", it should run itself automatically!
Click to expand...
Click to collapse
It looks as though the files are for a Linux system. Would this work on Windows 7?
Update: I copied the files to my C:\adb directory and it worked fine, my MediaPad is now rooted.
HDMI out working properly? and Flash playback in the browser?
Went back to HC because of that...
Nutsonfire said:
HDMI out working properly? and Flash playback in the browser?
Went back to HC because of that...
Click to expand...
Click to collapse
Yup, both HDMI and Flash work fine.
hansoho said:
Yup, both HDMI and Flash work fine.
Click to expand...
Click to collapse
well, there's a difference between "working" and "working as it should"
i don't have very good experience with HDMI output on ICS... when you look at this topic http://forum.xda-developers.com/showpost.php?p=23763131&postcount=12 , you can find my post about this in detail..
Klacik said:
well, there's a difference between "working" and "working as it should"
i don't have very good experience with HDMI output on ICS... when you look at this topic http://forum.xda-developers.com/showpost.php?p=23763131&postcount=12 , you can find my post about this in detail..
Click to expand...
Click to collapse
Ah I see what you mean. The HDMI output does look low-resolution with jagged edges.
But the HDMI test makes no difference for me whether the box is checked or not. Also, it doesn't matter whether the HDMI cable is connected before or after turning HDMI on.
Anyway, I hardly use it.. just a gimmick for me.
hansoho said:
Ah I see what you mean. The HDMI output does look low-resolution with jagged edges.
But the HDMI test makes no difference for me whether the box is checked or not. Also, it doesn't matter whether the HDMI cable is connected before or after turning HDMI on.
Anyway, I hardly use it.. just a gimmick for me.
Click to expand...
Click to collapse
i see
but a lot of people would like to use it as output for videos/games and it does look bad right now :\
it worked in HC, so i think it will be solved sooner or later..
Klacik said:
i see
but a lot of people would like to use it as output for videos/games and it does look bad right now :\
it worked in HC, so i think it will be solved sooner or later..
Click to expand...
Click to collapse
I'm sure it will be resolved soon. So far, Huawei has been quite responsive in updating their software.
Have you noticed any issues with this ICS yet?
If you did the last ICS update and rooted it (from a few weeks ago) can you skip rooting this time and just update?
that's an old build... flash this one! http://forum.xda-developers.com/showthread.php?t=1544855
lilaliend said:
If you did the last ICS update and rooted it (from a few weeks ago) can you skip rooting this time and just update?
Click to expand...
Click to collapse
I think you will need to root again. Which doesn't take that long..
Can you write instruction how root? I can't root new ICS ;/
edit: all good. When I off HiSuit I root device
octpus said:
First time posting........ here is the International Version of latest ICS 4.0.3 RC released on Mar 26: S7-301u_V100R002C002B008
Huawei did an excellent job in tunning ICS, it is very fast, stable and incorporates some of the latest features! Here's the download link!
S7-301u_V100R002C002B008
http://www.uploadstation.com/file/GXPgCZF/S7-301u_Intl_V100R002C002B008.rar
Latest One Key root for Mediapad
http://www.uploadstation.com/file/gX69WT8/4.0_One_Key_root.rar
Flash method : Unzip the downloaded .rar file and place the "dload" folder on the root of the SDCARD, reboot and whala~~ enjoy
Note: I am not responsiblt if you somehow screw up your device!!!
Click to expand...
Click to collapse
Today An update to the version of the S7-301u_ V100R002C002B009. Update is done via built-in updating system Huawei. But I do not know what changed from the previous version.
just updated to V100R002C002B009.
touch screen respone greatly improve around the 4 edges.
too bad hdmi output problem not fixed.
just to check anyone successfully overclock mediapad pad to 1.5ghz?
Question 1: For someone who just acquired a T-Mobile Springboard, how would said person go about installing this rom?
Question 2: If I insert a AT&T sim card into this devices that's still running the T-Mobile rom, will I be locked from using AT&T's 3G? I'm pretty certain the Springboard has the frequency support necessary to run on AT&T's 3G.
WingCero said:
Question 2: If I insert a AT&T sim card into this devices that's still running the T-Mobile rom, will I be locked from using AT&T's 3G? I'm pretty certain the Springboard has the frequency support necessary to run on AT&T's 3G.
Click to expand...
Click to collapse
If you insert an AT&T SIM you will get prompted for an unlock code, and won't be able to use on AT&T without it. If you have been a t-mobile customer for 60 days you can request the code from them. I have only been a customer for 30 days so haven't been able to get a code and verify operation on AT&T.
v35lee said:
If you insert an AT&T SIM you will get prompted for an unlock code, and won't be able to use on AT&T without it. If you have been a t-mobile customer for 60 days you can request the code from them. I have only been a customer for 30 days so haven't been able to get a code and verify operation on AT&T.
Click to expand...
Click to collapse
Is that the same situation if I (somehow) get the international rom onto this device?
From many many different threads and frankly confusing instructions I think I have puzzled together the following solid guideline for my kindle fire hdx from basic root to custom rom. Currently my firmware is 13.3.1.0.
Could someone take a look at this and tell me if I got this right or if I need to do stuff differently (or could do them better)? Don't assume that something is obvious, if it isn't written down, don't be shy to mention it. I would be ever so grateful .
Edit: I'm updating my experience as I move along the list and get more info just in case this might be useful to someone who is just as lost as I was in the beginning
Obligatory disclaimer: this is just a step-by-step guideline that worked for me. I'm not responsible if you chose to follow any of these steps and damage or brick your device.
Guideline:
-Download firmware version 3.2.3.2 and upgrade directly from any of the previous version by putting the file into the internal storage of the kindle, going to settings>device>system update on the kindle and installing the update from there.
-Root with Towelroot in the HDX toolkit downloaded from here (Edit: I got various error messages at this step but got it to work in the end. The 3rd post here shows what I did to get it working after getting error message 2 and 3 at various times)
-block OTA also with the tool in the HDX toolkit (is there a way to safely check that this worked? Edit: It worked )
-connect to wifi and install Flashify from the playstore (Edit: I ended up installing File Expert and flashify on another android device, backing up the flashify apk and sideloading it with ES File Explorer from the amazon app store to the kindle, I guess I could have also download the apk somewhere but I have trust issues.)
-download the img of TWRP 2.8.5.0. and put it in internal storage of kindle (had no problems)
-use flashify to save original stock recovery (had no problems)
-Use flashify to flash TWRP (had no problems)
- Boot into recovery mode via flashify to see if it worked (had no problems)
Now either A)
-download CM11 image and gapps and put the zip files on internal storage
-Edit: disconnect Kindle from USB afterwards
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- flash cm11 image and gapps (under install and then find them in the files)
- reboot
-Edit: I had the wifi not connecting problem that some people have with CM11 but a reboot took care of it.
-Edit 2: I couldn't get the kindle app to work on CM11 (it wouldn't synch my books, the device wasn't recognized by amazon and it would crash every time I logged in.) so I ended up replacing it with the Nexus rom. If the chance of this happening doesn't bother you then CM11 seems to still be a good choice.
or B)
- download HDX thor nexus rom and gapps and put the zip files on internal storage
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- Edit: disconnect Kindle from USB afterwards
- flash nexus rom and gapps (under install and then find them in the files)
- reboot
- Edit: I'm very happy with it, it works flawlessly. Since it's based on Jelly Bean I may try replacing it with another rom sometime in the future, but I'm in no hurry
Mostly correct, you can update directly to 3.2.3.2 no need for incremental steps. The only way to know if ota blocker worked is to check for update but there's really no need, as soon as you've run towel root just disable WiFi as it won't be needed anymore.
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
uhraman said:
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
Click to expand...
Click to collapse
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
derpadoodle said:
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
Click to expand...
Click to collapse
Thanks for your replies! Is the method uhraman hinted at the better one?
snorklm said:
Thanks for your replies! Is the method uhraman hinted at the better one?
Click to expand...
Click to collapse
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
derpadoodle said:
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
Click to expand...
Click to collapse
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
snorklm said:
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
Click to expand...
Click to collapse
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Davey126 said:
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Click to expand...
Click to collapse
Thanks for the sound advice, I will probably never feel comfortable enough for that , especially because I haven't achieved much at all yet. I haven't even flashed TWPR yet.
Yay, I did it. CM11 seems to be working as intended! Thanks again for everyone who replied and also to everyone who put so much work into making and improving all the tools and software necessary to make this kind of thing even possible, I appreciate it!
What firmware were you on to begin your process mate... ?
B3NJY said:
What firmware were you on to begin your process mate... ?
Click to expand...
Click to collapse
I was on 3.0.5 when I got the device. Amazon didn't upgrade the firmware at all before sending it out, then I upgraded to 13.3.2.3. Why do you ask?
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
snorklm said:
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
Click to expand...
Click to collapse
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Davey126 said:
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Click to expand...
Click to collapse
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
snorklm said:
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
Click to expand...
Click to collapse
Glad to hear everything is working well! My daily driver is on Nexus and I could not be happier. Everything works as it should. No need to unlock the bootloader unless you plan to do more modding. Enjoy your device!
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
johnwaters said:
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
Click to expand...
Click to collapse
Agreed, I was overwhelmed by all the different threads and possibilities at first. I ended up approaching it like any other research project for a paper or presentation and dumped every solid (and recent) piece of good advice into Evernote and sorting it out there. But writing and updating guides (especially with the fast development I have observed) would be a lot of work, I understand completely why no one would volunteer to do it and everybody would rather answer questions on a case by case basis.
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
dynein said:
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
Click to expand...
Click to collapse
First thing you want to do is block OTA (over the air updates) or your device may be upgraded by Amazon to a level that gives you less options. Suggest using HDX Toolkit (here) to both root and block OTA. Then install twrp (here). From there you can opt to replace Fire OS will several different roms including Nexus, CM11 or CM12.
Flashify is an app that allows flashing recovery and roms from from within Android vs adb or a recovery environment. You can grab it from the Play store or another market. It's a dangerous tool; use with extreme caution.
Be aware that any of the above actions, if executed incorrectly, can permanently brick your device with little/no hope of recovery (guess that's the definition of permanent). Read, read and read some more before taking any action. Be sure to keep WiFi off on your device until OTA is blocked to prevent auto-updates.
Root and S-Off Recommended
For S-Off look here then follow directions for permanent root in the development forum
1. Download a file explorer with root-browsing capabilities like Root Explorer or ES File Explorer from the Play Store
2. Using the file explorer you downloaded above, head over to /system/customize/ACC folder and open the default.XML file using any text editor.
3. Navigate to the following code near the bottom of the file:
<app name=”Tethering_provision”>
<item type=”integer”name=”TetheringGuard_rule”>3</item></app>
Notice the “3” above in bold. Change it to “0.” Save the edited text file and exit the app.
4. Reboot
Go into settings, enable WiFi Hotspot and it'll turn on. I did this on my At&t Desire 610, I assume other carriers can use the same method.
If Hotspot fails to initialize after being turned off, reboot your phone. I only came across this problem once.
Disclaimer/Piece of Mind: Most plans have data cap and tethering may and will consume data and possibly incure extra charges. I take no responsibility for what you do to your phone or consequences from said mod. :good:
Why is s off required? I'm trying to do this with my 510 and I hope the procedure is similar.
Bobby060 said:
Why is s off required? I'm trying to do this with my 510 and I hope the procedure is similar.
Click to expand...
Click to collapse
S-OFF is required to remove the write protection. I tried 5+ times to do this without S-off and every time it reverted back after rebooting. When you purchase S-OFF, it lets you save it permanently. $25 is a small price to pay to have tethering unlocked.
If you can make it work with S-on then I'll edit the OP. In my experience trying to write to the system will reboot the phone.
Bobby060 said:
Why is s off required? I'm trying to do this with my 510 and I hope the procedure is similar.
Click to expand...
Click to collapse
Let me know how it goes.
Isnt there a kernel that removed the write protect?
It doesn't work on my 510. I don't have soff, but I have a custom kernel with write protection removed, so the change persists across boot. Goodness, I'd hoped this would solve my problem.
godkillerz223 said:
Isnt there a kernel that removed the write protect?
Click to expand...
Click to collapse
Its never worked for me. That's why I say S-off, it makes things so much easier.
godkillerz223 said:
Isnt there a kernel that removed the write protect?
Click to expand...
Click to collapse
the Jmz kernel does remove the write protection, and if you can deal with the various bugs that come along with it, than you'll be fine. Personally, I couldn't handle the periodic freezing so I ponied up the $25.
phatmanxxl said:
If you can make it work with S-on then I'll edit the OP. In my experience trying to write to the system will reboot the phone.
Click to expand...
Click to collapse
I changed it and it didnt reboot the phone but it needs reboot to stick (i think) and it doesnt stay at "0"
Can someone with jmz kernel please give it a shot? I dont use it anymore but bugs seemed to be minimal when i was running old firmware. Thanks.
$25 for this phone is a little steep. If it meant even one good custom rom id fork it over but Im thinking the price tag makes more sense for the flagship users. However, im still looking for a good reason...
KLit75 said:
I changed it and it didnt reboot the phone but it needs reboot to stick (i think) and it doesnt stay at "0"
Can someone with jmz kernel please give it a shot? I dont use it anymore but bugs seemed to be minimal when i was running old firmware. Thanks.
$25 for this phone is a little steep. If it meant even one good custom rom id fork it over but Im thinking the price tag makes more sense for the flagship users. However, im still looking for a good reason...
Click to expand...
Click to collapse
Unless your S-off the changes won't stick during a reboot, I'm surprised the phone even let you get that far, as far as modifying the XML file. I'm working on a debloated ROM with this mod cooked in. Anybody want to test it for me? I'll upload it now to my drop box.
phatmanxxl said:
Unless your S-off the changes won't stick during a reboot, I'm surprised the phone even let you get that far, as far as modifying the XML file. I'm working on a debloated ROM with this mod cooked in. Anybody want to test it for me? I'll upload it now to my drop box.
Click to expand...
Click to collapse
Yes. It let me edit it--there might be a mod im using that allows that? But went right back to 3 after reboot.
KLit75 said:
Yes. It let me edit it--there might be a mod im using that allows that? But went right back to 3 after reboot.
Click to expand...
Click to collapse
My internet was shut off for a few days so I was desperate to find out how to use my phone as a hot spot, I knew there was a way. This was the only working solution I was able to find.
phatmanxxl said:
If you can make it work with S-on then I'll edit the OP. In my experience trying to write to the system will reboot the phone.
Click to expand...
Click to collapse
Just playing around...this does work with jmz kernel. I flashed the deodexed rom last night and its way too early but no bugs so far. Instead of kk sd fix i used twrp manager and applied the sd patch. Im also using seeder.apk (which is free right now) The rom has busybox built in so installing your own could exacerbate bugs, maybe?
Most of the bugs i experienced with the kernel were tied somehow to the audio jack. That seemed to trigger crazy behavior like auto calling, voice google searches.
Tethering is good to have but my data plan sucks. I was hoping to use it as sort of a bridge for weak wifi spots but i find the wifi on the 610 is much slower than even older devices i own.
This setup probably wont be ideal for daily use but i feel like this would be a really good phone if it had some development.
I'm running stock, rooted with Xposed. No problems here. I've read people having various issues with JMZ Kernel.
Yea this phone is slow, a good Lollipop ROM would do wonders for the 610.
AT&T HTC Desire in Venezuela
i bought this phone, and im crazy trying to get sd fix, s-off and wifi tethering enable plz somebody help me, i already unlcok the bootloader trought hctdev and fastboot, i rooted but i can do tethering and i need it to share internet on my tablet for work. there's no a zip custom rom with all the fixes we need for this model? plz help me!
victormnavaso said:
i bought this phone, and im crazy trying to get sd fix, s-off and wifi tethering enable plz somebody help me, i already unlcok the bootloader trought hctdev and fastboot, i rooted but i can do tethering and i need it to share internet on my tablet for work. there's no a zip custom rom with all the fixes we need for this model? plz help me!
Click to expand...
Click to collapse
If you get s-off from sunshine, I think it'll unlock and root, but I believe you need to be locked and unrooted first. I'm not s-off so not certain. Once you are s-off, the WiFi tethering is simple. The one stipulation is it costs $25--a lot IMO since we really have no development on this phone.
If you read my earlier post in this thread, I was able to enable WiFi tethering and write to sdcard with s-on by flashing the jmz and stock deodexed firmware and jmz kernel which removes write protection. Most people don't do that because lots of bugs have been reported. So if you're willing to pay, checkout sunshine installer.
Btw--its been about a week and my phone has been fine (no freezes and no erratic behavior when plugged into audio jack) Its not super fast but this phone wasn't really fast to start. Your results may differ. My setup procedure is a little different. Instead of kk sdcard fix I use twrp manager and set the patch. The rest was a lot of trial & error and I lost track of exactly how I arrived here, but its been working fine for me.
I can't buy Sunshine form root ninja!
The support of ninjaroot told me that i can't buy their products for ppl of Venezuela, even having amazon gift card credit. y really need to unlock this awfull at&t limits, the freedom of using tethering and can use Quickpic as a default gallery and erase pics, further can manage the sd card, install xposed and all the stuff we can do in a normal Android phone. Plz if you can help me wiht this? it's really hard for us my country to get cellphones from US due ecommerce restrictions in our credit cards. how can i sd fix via twrp as you did?
victormnavaso said:
The support of ninjaroot told me that i can't buy their products for ppl of Venezuela, even having amazon gift card credit. y really need to unlock this awfull at&t limits, the freedom of using tethering and can use Quickpic as a default gallery and erase pics, further can manage the sd card, install xposed and all the stuff we can do in a normal Android phone. Plz if you can help me wiht this? it's really hard for us my country to get cellphones from US due ecommerce restrictions in our credit cards. how can i sd fix via twrp as you did?
Click to expand...
Click to collapse
That sucks. Well the only thing I can tell you is what I used right here in this forum BUT while I know the kernel works on international version, I'm not 100% on the stock deodexed rom. Do whatever research you can. Click "downloads" in the first post then pick our phone from the list. Flash the rom (which is rooted and has busy box built in, then flash the kernel)
http://forum.xda-developers.com/desire-610/development/att-stock-rooted-odex-deodex-t2848774
KLit75 said:
That sucks. Well the only thing I can tell you is what I used right here in this forum BUT while I know the kernel works on international version, I'm not 100% on the stock deodexed rom. Do whatever research you can. Click "downloads" in the first post then pick our phone from the list. Flash the rom (which is rooted and has busy box built in, then flash the kernel)
http://forum.xda-developers.com/desire-610/development/att-stock-rooted-odex-deodex-t2848774
Click to expand...
Click to collapse
I'm willing to try that, so tell me something where i can download the patch of sdcar writing to patch via twrp?
---------- Post added at 02:21 AM ---------- Previous post was at 01:57 AM ----------
Hey guyz i just flash the jmz kernel and did the guide to unlock tether, installed xposed and now i got tethering unlocked adn can erase things from sd card, im using quickpic as my default gallery and very happy thanks for doing this possible! MANY THANKS! :laugh:
Just got my phone yday. I've scoured the Ascend Mate2 threads, and al I see are questions about re-rooting the Lollipop build. Since it looks like Huawei has rescinded their Lollipop ROM for the moment, I'm just hanging on 4.3. With a screen this HUGE, I'd love to root to be able to lower the DPI. Can anyone advise how to do that? Or am I better just waiting for Huawei to officially release Lollipop?
EDIT: so I found this -- http://forum.xda-developers.com/showpost.php?p=61682526&postcount=3. I'm confused, cuz one page of Huawei's blog says they hit pause on the 5.1 rollout, yet this 5.1 download looks like it's hosted on GetHuawei.com. I'm so confused...
adogg222 said:
Just got my phone yday. I've scoured the Ascend Mate2 threads, and al I see are questions about re-rooting the Lollipop build. Since it looks like Huawei has rescinded their Lollipop ROM for the moment, I'm just hanging on 4.3. With a screen this HUGE, I'd love to root to be able to lower the DPI. Can anyone advise how to do that? Or am I better just waiting for Huawei to officially release Lollipop?
EDIT: so I found this -- http://forum.xda-developers.com/showpost.php?p=61682526&postcount=3. I'm confused, cuz one page of Huawei's blog says they hit pause on the 5.1 rollout, yet this 5.1 download looks like it's hosted on GetHuawei.com. I'm so confused...
Click to expand...
Click to collapse
Since you just got your phone, I would say get to know it on 4.3 first. Lollipop is prettier, but you can do more root things on JB, it runs better, has better battery life, and is an all around better experience, IMO.
Lollipop doesn't have xposed either, if you planned on using that. On top of that, it is missing some core functionality like a startup manager(apps that should be running after a reboot are not!) and has a crippling audio bug.
First thing you have to do for root is email Huawei with your IMEI and SN asking for a bootloader unlock code.
[email protected]
Here is the email I sent them:
Hello, I would like a code to unlock the bootloader on my Huawei Ascend Mate 2, please.
Serial - *********
IMEI - *******
Thank you
Click to expand...
Click to collapse
I then got an unlock code within minutes, so it may or may not be somewhat automated.
TWRP for Mate2
Basically that is a zip file with everything that you need to install TWRP on the Mate2. It has:
SHM's Unified TWRP(v2.8.7.3).
Huawei drivers
ADB/Fastboot
SuperSu(v2.46)
stock 5.1 recovery(just incase)
!Readme file with step by step.
TWRP is needed to install SuperSu, which in turn gives you root.
First, make sure you leave all the files in the same folder. Extract them anywhere, like your desktop. Install the Huawei drivers if you don't already have them installed.
***Put the UPDATE-SuperSU-v2.46.zip on your phone's sdcard somewhere easy to find***
1. Turn off your phone
2. Hold Volume DOWN and Power button for a few seconds. When the screen turns on let go of the power button.
3. Now you should be on the bootloader screen, also known as fastboot.
4. Plug your phone into your PC and wait a minute to make sure any additional drivers are installed and setup.
5. Hold shift and right click an empty space in the folder you downloaded with adb.exe and fastboot.exe and select "Open command window here". A command window should open.
6. In command window type 'fastboot devices' and make sure it says there is a fastboot device. If it doesn't, that means your drivers didn't work. Try unplugging your phone and using another USB port.
7. If it showed a device, its working. Type 'fastboot flash recovery twrp.img'
8. If successful, your phone now has twrp installed
9. While still in fastboot, hold VOLUME UP and the POWER BUTTON for about 8 to 10 seconds, as soon as the screen turns off and then back on again, let both buttons go.
10. In TWRP, hit install and find your UPDATE-SuperSU-v2.46.zip and flash it.
11. Should be rooted and good to go.
12. I included the stock recovery if you ever want/need to go back. Just follow the same steps but replace "twrp.img" with "stock_recovery.img"
Click to expand...
Click to collapse
To lower DPI on our phone, a line will need to be added to the build.prop in the "root/system/" directory.
Add:
Code:
ro.sf.lcd_density=264
to the end of the text on a new line. 264 is the lowest you can go without causing multiple apps to crash.
You can go lower, but you will need Xposed and App settings to change the crashing apps to 264 or above.
Wow, thank you SO much for all of this!! So awesome of you!
adogg222 said:
Wow, thank you SO much for all of this!! So awesome of you!
Click to expand...
Click to collapse
Build prop editor on Google play store can very easily change your dpi. And makes a backup if you want to go back. Better than modding it yourself. And I agree with ark. Hold.off on L until things are fixed. Or until Tom get cm12 up and going.
Props to Ark for putting so much effort into his reply. (I would not have done the same.)
My advice to this self proclaimed "noob" is to read the threads and get more educated before just posting a question that has already been answered with it's own thread. All of the info that Ark posted is in these forums. Please don't get in the habit of asking to be spoon fed. That is certainly frowned upon on XDA.
kimtyson said:
Props to Ark for putting so much effort into his reply. (I would not have done the same.)
Click to expand...
Click to collapse
I had most of it done and copy pasted from another post I already made.
I'm glad someone finally gave simple comprehensive instruction. Unlike someone stated above, it was not that easy to find. I have had my phone for about 1 1/2 months since I returned from vacation in Europe. Ordered it online from Frys while I was there. Anyway, I have searched many times for instructions and couldn't find one thing definitive. Always comments alluding to root, and "does this keep root after update" or "how to get root back" or "this root method didn't work" etc... But never could I find instructions on how to achieve root on stock 4.3 until now. So Thank you sooo much. Now are we sure about the email link you provided above? Because I sent them (Basically copy and pasted ) your email above email twice. About a week ago, and a few days ago. And still no response! Any other suggestions? And shouldn't this be stickied since Root is the most basic of function of what we all want?
Some great information in this thread. Thanks guys. So unlocking the bootloader will wipe the device correct?
I got my unlock code and was going to unlock and make the device see itself as OEM. I was going to install L but it sure seems from the few posts here that it might not be worth it. Crippling audio bug? Can anyone elaborate on that?
Would it be better to unlock, convert my device to OEM and register with Huawei for OTA updates and simply wait for an official release? If I do the conversion, will the OS still be 4.3 at least?
Just like the thought of the updated Huawei EMUI 3 1.
I'm reading so many different confusing post. So does towelroot or kingroot work on MT2 L03 Android 4.3? I've read other places those methods work? And does anyone have the instructions on the easiest way to unlock bootloader (I hear that is necessary before we root)? I already have the unlock code. This phone has been in a box for the last 1 1/2 months waiting for me to have the time to play. Thank you.
TheIgster said:
Some great information in this thread. Thanks guys. So unlocking the bootloader will wipe the device correct?
I got my unlock code and was going to unlock and make the device see itself as OEM. I was going to install L but it sure seems from the few posts here that it might not be worth it. Crippling audio bug? Can anyone elaborate on that?
Would it be better to unlock, convert my device to OEM and register with Huawei for OTA updates and simply wait for an official release? If I do the conversion, will the OS still be 4.3 at least?
Just like the thought of the updated Huawei EMUI 3 1.
Click to expand...
Click to collapse
The audio bug is a bug that happens while listening to any audio. The audio will cut off completely. If you press the either of the volume keys, the phone will basically freeze for around 30 seconds and then usually it starts working like normal again.
It happened to me very often, like every time I listened to anything. But after installing Viper and its drivers and boosting the audio levels I haven't had this bug happen once. So that seems like a fix to me.
---------- Post added at 11:41 PM ---------- Previous post was at 11:36 PM ----------
TTJB said:
I'm reading so many different confusing post. So does towelroot or kingroot work on MT2 L03 Android 4.3? I've read other places those methods work? And does anyone have the instructions on the easiest way to unlock bootloader (I hear that is necessary before we root)? I already have the unlock code. This phone has been in a box for the last 1 1/2 months waiting for me to have the time to play. Thank you.
Click to expand...
Click to collapse
If you have the code, just boot into fastboot and use the command
Code:
fastboot oem unlock *your code, no asterisks*
ArkAngel06 said:
The audio bug is a bug that happens while listening to any audio. The audio will cut off completely. If you press the either of the volume keys, the phone will basically freeze for around 30 seconds and then usually it starts working like normal again.
It happened to me very often, like every time I listened to anything. But after installing Viper and its drivers and boosting the audio levels I haven't had this bug happen once. So that seems like a fix to me.
Click to expand...
Click to collapse
Hmmm. I have finally loaded LP, but haven't messed too much with audio playback. I'll have to listen for it. So where is this viper that I can load?
TheIgster said:
Hmmm. I have finally loaded LP, but haven't messed too much with audio playback. I'll have to listen for it. So where is this viper that I can load?
Click to expand...
Click to collapse
It's on Google Play or XDA. Try looking for it.
kimtyson said:
It's on Google Play or XDA. Try looking for it.
Click to expand...
Click to collapse
Thanks. Maybe try being less snarky next time?
Just a simple question in a forum that doesn't have a helluva lot of posts anyway.
alright so i got to the stage where i have superSU. however when i open it it says SU binary needs to be updated
i tried using twrp and installed the updated 2.4.6....and it still says i need to update the binary
any suggestions?
thanks ark for the detailed instructions tho
Callmebaus said:
alright so i got to the stage where i have superSU. however when i open it it says SU binary needs to be updated
i tried using twrp and installed the updated 2.4.6....and it still says i need to update the binary
any suggestions?
thanks ark for the detailed instructions tho
Click to expand...
Click to collapse
Just let it update itself.
Moody66 said:
Just let it update itself.
Click to expand...
Click to collapse
how? selecting normal? instead of twrp?
Callmebaus said:
how? selecting normal? instead of twrp?
Click to expand...
Click to collapse
Normal
jesus christ i remember normal fkin up my phone so i was sure not to press it then i formatted my phone using twrp
os....as well
I can't do anything
i should shoot myself.
trying to install stock again, having no luck
Callmebaus said:
jesus christ i remember normal fkin up my phone so i was sure not to press it then i formatted my phone using twrp
os....as well
I can't do anything
i should shoot myself.
trying to install stock again, having no luck
Click to expand...
Click to collapse
If you still not resolve the problem yet, try this:
http://forum.xda-developers.com/showpost.php?p=58208866&postcount=9
and remember always take backup...
xordos said:
If you still not resolve the problem yet, try this:
http://forum.xda-developers.com/showpost.php?p=58208866&postcount=9
and remember always take backup...
Click to expand...
Click to collapse
that's the exact post that I used yesterday, haha
all fixed and rooted
thank u
Ok so at first it wouldn't let me in until I plugged it into a computer or a fancy USB outlet. And it wouldn't let me go T the home screen. Now it wont let me on at all, after the home screen suddenly swooped in and ate this post on my Apollo, thus ****ing it. So now I can't get in at all. And I just rooted after I suddenly got this update, the newish one, and I renamed ota and ota contracts on accident. Is that a problem? Please help me...
Leafen said:
Ok so at first it wouldn't let me in until I plugged it into a computer or a fancy USB outlet. And it wouldn't let me go T the home screen. Now it wont let me on at all, after the home screen suddenly swooped in and ate this post on my Apollo, thus ****ing it. So now I can't get in at all. And I just rooted after I suddenly got this update, the newish one, and I renamed ota and ota contracts on accident. Is that a problem? Please help me...
Click to expand...
Click to collapse
Renaming OTA contracts is a problem! Given device is rooted it may be fixable via ADB. Also possible you can go further and unlock bootloader which yields complete control to repair/replace FireOS. I am travelling today and can not immediately help with details. Will check back later (24 hours) to see if help is still needed.
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Leafen said:
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Click to expand...
Click to collapse
Bootloop further complicates matters. How much time passes before the device restarts? Does it ever make it to the login screen?
While there is still a glimmer of hope the situation is dire. Pretty good chance the device can not be recovered. I say that not to be negative but rather recognizing Apollo is not a cheap gadget. Amazon crippled native recovery capabilities making simple fixes impossible to apply. Akin to making tires a non replaceable item (brilliant). Just want to prepare you for an unpleasant outcome...
Davey126 said:
Bootloop further complicates matters. How much time passes before the device restarts? Does it ever make it to the login screen?
While there is still a glimmer of hope the situation is dire. Pretty good chance the device can not be recovered. I say that not to be negative but rather recognizing Apollo is not a cheap gadget. Amazon crippled native recovery capabilities making simple fixes impossible to apply. Akin to making tires a non replaceable item (brilliant). Just want to prepare you for an unpleasant outcome...
Click to expand...
Click to collapse
Oi. Uh. It's normal procedure up to the colored Kindle logo. Goes off the same amount of time as usual. And it never makes it to the put in your password screen. Not yet anyways.
Scratch that I'm in. Changing Ota contracts back
It worked. I'm able to get back in the home screen. But now I need safestrap again for the ROM I already have partitioned on this device.
Leafen said:
It worked. I'm able to get back in the home screen. But now I need safestrap again for the ROM I already have partitioned on this device.
Click to expand...
Click to collapse
Great! Assuming a factory reset did the trick (I didn't immediately suggest that course of action as it can sometimes make things worse; other things to try first).
If you install Safestrap v4 choice of ROMs is limited to Fire Nexus and CM11 - both KitKat based. Unlocking the bootloader opens the door to a wider selection of Lollipop and Marshmallow based ROMs. Unlocking is not risky but does require a bit of technical knowledge and some patience. An unlocked device is also easier to recover in the event of a ROM crash or bootloop.
Assuming you want to proceed with Safestrap download the app from here. Make sure you get the build appropriate for your device. Install/launch the app and then select the option that installs Safestrap recovery. Please note this is not a true recovery environment and has none of the special powers associated with TWRP. Its singular purpose it to support the two custom ROMs noted above on a locked device. Unlocked devices do not need to use Safestrap.
Once Safestrap recovery is installed reboot your device. After the grey Amazon logo you will be presented with a 'robot' screen where you can choose to continue booting into FireOS or enter Safestrap recovery mode. Choose the latter. After a few moments device will enter Safestrap recovery which emulates TWRP.
Do you know what to do from here?
Warning: Once Safestrap v4 recovery is installed you should NEVER perform a factory reset via the stock recovery menu. Doing so will brick the device.
Oh! Well. Id like to know about unlocking my boot whatever. Now Marshmallow and lollipop are Android 4. S.omething right? Oh um. Do you mind telling me how to do it, especially since I got jammed into the new update, breaking my safestrap I already had and leaving the slot out to dry? That would be appreciated!
Leafen said:
Oh! Well. Id like to know about unlocking my boot whatever. Now Marshmallow and lollipop are Android 4. S.omething right? Oh um. Do you mind telling me how to do it, especially since I got jammed into the new update, breaking my safestrap I already had and leaving the slot out to dry? That would be appreciated!
Click to expand...
Click to collapse
Well you got "jammed" into a FireOS update because Safestrap was improperly configured. Details matter. Suggest proceeding with reinstalling Safestrap and forget about unlocking the bootloader thingy. Do not create or attempt to use a secondary slot. Custom ROM overwrites FireOS in the stock slot. Lots of posts outlining Safestrap best practices that apparently were not read or ignored.
Bootloader unlock thread: http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
No the reason I was booted out was because i was having to be stuck on the FireOS because I have to have it for well.. Showing reasons. Don't worry about that. But Safestrap was done perfect, I had it going on for A long while. I successfully used two or more ROMs with perfect functionality.
Leafen said:
I successfully used two or more ROMs with perfect functionality.
Click to expand...
Click to collapse
If using multiple/secondary slots worked well enough for you, great!
Full functionality can not be achieved in secondary slots with Safestrap v4 which is an adaptation specific to this device and was never intended to support dual boot capability. Issues impacting ROMs operating in secondary slots:
- restricted BT/WiFi radio functionality (less of an issue w/CM11)
- only 2 of 4 CPU cores available (other two disabled)
- the two active cores run at 100% regardless of load
- device will not enter deep sleep when secondary slot is active
- poor performance and lousy battery life resulting from above
If you only use the secondary slot on occasion and radios work then it's obviously a personal call if the limitations are problematic.
Davey126 said:
If using multiple/secondary slots worked well enough for you, great!
Full functionality can not be achieved in secondary slots with Safestrap v4 which is an adaptation specific to this device and was never intended to support dual boot capability. Issues impacting ROMs operating in secondary slots:
- restricted BT/WiFi radio functionality (less of an issue w/CM11)
- only 2 of 4 CPU cores available (other two disabled)
- the two active cores run at 100% regardless of load
- device will not enter deep sleep when secondary slot is active
- poor performance and lousy battery life resulting from above
If you only use the secondary slot on occasion and radios work then it's obviously a personal call if the limitations are problematic.
Click to expand...
Click to collapse
I only had the battery thing. Otherwise I used my secondary rom pretty much all the time.
Leafen said:
I only had the battery thing. Otherwise I used my secondary rom pretty much all the time.
Click to expand...
Click to collapse
And ½ the CPUs disabled. So why not install the custom rom in the stock slot?
Davey126 said:
And ½ the CPUs disabled. So why not install the custom rom in the stock slot?
Click to expand...
Click to collapse
I have o keep up appearances pretty much. The reason why I dont really need to tell you. But its for appearences sake
Leafen said:
I have o keep up appearances pretty much. The reason why I dont really need to tell you. But its for appearences sake
Click to expand...
Click to collapse
Yep - I get it. Not specifics (obviously) but understand optics. As an aside unlocking the bootloader offers no significant benefit given your situation. Enjoy.
Davey126 said:
Yep - I get it. Not specifics (obviously) but understand optics. As an aside unlocking the bootloader offers no significant benefit given your situation. Enjoy.
Click to expand...
Click to collapse
Crap. Safestrap isnt working for this update. Dang. Gotta wait for ggow or someone to make it.
Leafen said:
Crap. Safestrap isnt working for this update. Dang. Gotta wait for ggow or someone to make it.
Click to expand...
Click to collapse
Must be on FireOS 4.5.2.0 or 4.5.5.1 to run Safestrap v4. Rollback/upgrade options are available but ugly. Pretty sure Safestrap won't be receiving any further updates now that the HDX bootloader can be unlocked on any rooted 3rd gen device.