These are pure AOSP builds by dhacker29, all credit goes to him.
Please note these are hot off the press and may have bugs. Users have reported trouble with flashing, etc, but when you manage to get it to run the ROM runs smoothly.
Still, AOSP is bare-bones and will need device specific modifications that custom ROMs provide. Consider it a stable-ish alpha build, but not a dependable daily driver.
Please ensure you do your backups. Nobody is responsible if your phone bursts into flames.
All files you need are here:
Prerequisites: KitKat requires TWRP 2.6.3.0 which can be found here
xt925 ROM
xt926 ROM
GAPPS
By default AOSP has no root access, however Chainfire's root will work just fine. Just flash and install SuperSU.
Have fun with KitKat!
Changelog
20131108 Fix sd-mount, update blobs with 4.4 MotoX leak
Known Issues:
Ext-SD not activated
As with other AOSP builds, Google Keyboard is not working. Make sure to use AOSP keyboard.
Does not work with 16GB internal storage https://twitter.com/dhacker29/status/398946262172446720 (Try different versions of TWRP to address this)
Front camera may not work - will crash camera app. Go to app info and clear data to run it again
Video playback problems for some
Some HDMI problems when plugged in
I'm pretty happy on CM 10.2, but I may have to flash this just to see what 4.4 is all about...
Thanks for sharing! :good:
Thanks for sharing.
From a comment on twitter, it looks like the external SD card doesn't work. Just an FYI for those who are flashing.
Sent from my XT926 using Tapatalk
Just tried to flash the ROM using CWM... obviously didnt work lol.
Flashed TWRP 2.6.3.0, then flashed the ROM
Setting up device now.
Ill post after a day or so of usage to let everyone know how its going.
TXKSSnapper said:
From a comment on twitter, it looks like the external SD card doesn't work. Just an FYI for those who are flashing.
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
You got right.
Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.
madmonkey57 said:
Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.
Click to expand...
Click to collapse
Worked fine for me, it's how I flashed it in the first place. How did it fail on your end?
dabanhfreak said:
Worked fine for me, it's how I flashed it in the first place. How did it fail on your end?
Click to expand...
Click to collapse
do you mind editing the OP to include a list of known issues?
Thanks!
koftheworld said:
do you mind editing the OP to include a list of known issues?
Thanks!
Click to expand...
Click to collapse
Yet to run into any tbh (besides ex-SD of course), will give it about 24hours and see what folks pick up.
koftheworld said:
do you mind editing the OP to include a list of known issues?
Click to expand...
Click to collapse
Got stuck on the M Logo. But now, I'm wondering if it's not the infamous "Stuck on the M Logo" bug more than the recovery not working on the XT925. I'll try again.
madmonkey57 said:
Another FYI. TWRP 2.6.3.0 in the first post does not work on the XT925.
Click to expand...
Click to collapse
I just fastboot TWRP 2.6.3 now and it´s working flawlessly on XT925. I´m using it to do a backup right now before trying the wonderful Dhacker piece of work.
flight666 said:
I just fastboot TWRP 2.6.3 now and it´s working flawlessly on XT925. I´m using it to do a backup right now before trying the wonderful Dhacker piece of work.
Click to expand...
Click to collapse
Using Flashify. It flashes OK, but I can't get to the recovery... Hanging on the M logo. Damn it.
Can the atrix HD flash this??
Sent from my MB886 using xda app-developers app
Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------
madmonkey57 said:
Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
Click to expand...
Click to collapse
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.
madmonkey57 said:
Flashing TWRP 2.6.3.0 using Flashify --> Can't boot to the recovery, stuck on the M Logo
Flashing TWRP 2.6.3.0 using fastboot/USB cable --> Can't boot to the recovery, stuck on the M Logo
Flashing OUDhs CWM Touch Req0very v1.0.3.4 using fastboot/USB cable --> boot to the recovery OK
As it works for some other XT925s out there, something is wrong with mine...
---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.
Click to expand...
Click to collapse
Good to see
I'm noticing that there's a bug in the AOSP launcher, I can't seem to add a new home screen.
I installed the Nexus 5 Launcher as well, same result.
No such problems on Nexus 7 when installed Google Launcher.
EDIT: nvm, it seems that installing Google Launcher messes with the AOSP launcher... didn't make sense to me either. Oh well, no N5 experience
Uh, no, not that either. I think it was a custom Wallpaper.
you've to drag an app to make a new screen on the new kk launcher ?
pls correct me if i'm wrong..
madmonkey57 said:
Got it:
My twrp file was 8370KB whereas the actual file size is 8400KB... The first download failed and it missed the last 30KB...
I confirm TWRP 2.6.3.0 running on my device as well.
Click to expand...
Click to collapse
Great!
Now its me... having error on updater binary flashing the 4.4 ! lol
flight666 said:
Great!
Now its me... having error on updater binary flashing the 4.4 ! lol
Click to expand...
Click to collapse
Downloads are slow and tend to fail before the end... We'd better be careful! I am currently re-downloading all files needed.
Related
Hey Everyone the folks over at TEAM WIN RECOVERY PROJECT put together an image file for TWRP recovery for the I9505G. I take NO CREDIT for this but I did convert the image into an ODIN flashable .TAR file because an ODIN tar was not available on TWRP website. I have tested and flashed this on my Locked Bootloader and Stock Google Edition Galaxy S IV running 4.2.2. Please make sure you Unlock the Bootloader if you want to Root your phone, the Root will not work if you try to install it from Recovery on reboot.
As Always I am not responsible if you brick your phone doing any modification
HOW TO INSTALL
Open up ODIN and click on PDA
Select Recovery.tar from the attachment you downloaded
Make sure ONLY "AUTO REBOOT" is checked
Click START
After you see the PASS on Odin and "Removed" Unplug
Power Off or Pull the battery
Use Volume Up and the Power till you see the SAMSUNG logo and let go of all. Wait for TWRP to boot, it took a little longer so your not stuck, just be patient.
8/30/2023 / 2.6.1.0
10/14/2013 / 2.6.3.0
07/21/2014 / 2.7.1.0
UPDATED TWRP IMAGES AND .TAR ODIN FILES http://techerrata.com/browse/twrp2/jgedlte
-----------------------------------------
KNOWN ISSUES For 2.6.0.0 & 2.6.1.0: 8/31/2023 ( post any help info on further releases ) UPDATE 7/21/2014 I have not been using the I9505G for awhile now so I am not sure of any issues or bugs on the latest releases please post them in the thread.
I have used TWRP from the Team Win site and the Odin package image I put together here and I have noticed and reported 2 bugs. The first is you can get stuck on TWRP screen booting into recovery, just pull the battery or reflash again until it boots up. The second is that when you restore sometimes you will get a FAIL immediately, don't panic, (1) reflash a ROM, and Restore or (2), pull battery and reboot back into recovery and Restore or (3) wipe and then Restore.
This build has some minor issues but if you follow this guide you will be OK.
Thanks to the Folks at TEAM WIN RECOVERY PROJECT and Chahk
MJ (attached file is for 2.6.0.0) PLEASE DO NOT USE ATTACHED RECOVERY PLEASE USE THE LINK ABOVE FOR OFFICIAL TWRP RECOVERY
MJHawaii said:
Hey Everyone the folks over at TEAM WIN RECOVERY PROJECT put together an image file for TWRP recovery for the I9505G. I take NO CREDIT for this but I did convert the image into an ODIN flashable .TAR file because an ODIN tar was not available on TWRP website. I have tested and flashed this on my Locked Bootloader and Stock Google Edition Galaxy S IV running 4.2.2. Please make sure you Unlock the Bootloader if you want to Root your phone, the Root will not work if you try to install it from Recovery on reboot.
As Always I am not responsible if you brick your phone doing any modification
HOW TO INSTALL
Open up ODIN and click on PDA
Select Recovery.tar from the attachment you downloaded
Make sure ONLY "AUTO REBOOT" is checked
Click START
After you see the PASS on Odin and "Removed" Unplug
Power Off or Pull the battery
Use Volume Up and the Power till you see the SAMSUNG logo and let go of all. Wait for TWRP to boot, it took a little longer so your not stuck, just be patient.
Thanks to the Folks at TEAM WIN RECOVERY PROJECT and Chahk
MJ
Click to expand...
Click to collapse
Thank you! Will try it out after work. Have you tried to perform a full nandroid backup?
---------- Post added at 11:48 AM ---------- Previous post was at 10:57 AM ----------
I just installed it via Goomanager app. =)
Sent from my GT-I9505G using xda premium
taney said:
Thank you! Will try it out after work. Have you tried to perform a full nandroid backup?
---------- Post added at 11:48 AM ---------- Previous post was at 10:57 AM ----------
I just installed it via Goomanager app. =)
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
I did not try to do a Nandroid this was the image from Team Wins website so I don't think you will have any backup issues like some did with the I9505 image. Goo Manager is always the best option but a .tar comes in handy at times that is the only reason I converted their image.
Sent from my GT-I9505G using Tapatalk 2
This is big news, but the lack of replies has me worried. I need more brave souls to flash before me.
BTW, did this trip your counter MJ?
Apologies if I am completely wrong - but does this mean that if I use this recovery my phone will be 100% identical to the official S4GE? I assume that would make a lot more stable and efficient than the current dumbs we have been leaked?
Thanks in advance!
ldjalal said:
Apologies if I am completely wrong - but does this mean that if I use this recovery my phone will be 100% identical to the official S4GE? I assume that would make a lot more stable and efficient than the current dumbs we have been leaked?
Thanks in advance!
Click to expand...
Click to collapse
From my understanding this is just a TWRP recovery. It's not something that will make your phone a stock S4GE because this is a custom recovery. It's a custom recovery for the S4GE GT-I9505G.
qnet said:
From my understanding this is just a TWRP recovery. It's not something that will make your phone a stock S4GE because this is a custom recovery. It's a custom recovery for the S4GE GT-I9505G.
Click to expand...
Click to collapse
Ohh OK, so this is just a TWRP recovery for an official S4GE? Thank you for clearing that up.
jpculp said:
This is big news, but the lack of replies has me worried. I need more brave souls to flash before me.
BTW, did this trip your counter MJ?
Click to expand...
Click to collapse
I put everything in the OP guys this is just recovery you can flash from Odin. I have tested and flashed this on my own I9505G this is NOT for the I9505
Sent from my GT-I9505G using Tapatalk 2
Flashing the .img with Heimdall is another option.
EDIT: http://forum.xda-developers.com/showthread.php?t=2370101
irishrally said:
Flashing the .img with Heimdall is another option.
EDIT: http://forum.xda-developers.com/showthread.php?t=2370101
Click to expand...
Click to collapse
Odin is easier for most Windows users because of its GUI, using standard USB drivers, and not having to mess around with Command Prompt.
Chahk said:
Odin is easier for most Windows users because of its GUI, using standard USB drivers, and not having to mess around with Command Prompt.
Click to expand...
Click to collapse
I agree Heimdal is great but most people prefer and use Odin
Sent from my GT-I9505G using Tapatalk 2
Can any one confirm this is working ?
Anyone can confirm this works ? (GT-I9505G)
(backup and restore works ?)
Thanks
imneo1 said:
Anyone can confirm this works ? (GT-I9505G)
(backup and restore works ?)
Thanks
Click to expand...
Click to collapse
Backups work I have not tried to restore though
MJHawaii said:
Backups work I have not tried to restore though
Click to expand...
Click to collapse
Full restore as well as partial work fine.
Chahk said:
Full restore as well as partial work fine.
Click to expand...
Click to collapse
Yep I did multiple backups, restore, and even flashing test zips upcoming ROMs for the I9505G. Make sure your following us in the GENERAL section here in Discussion I9505G there is a lot happening.
http://forum.xda-developers.com/showthread.php?t=2381339
Sent from my GT-I9505G using Tapatalk 2
Edit...done
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Edit...done
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I have used odin to flash this TAR File and it passes but when I boot into my recovery it is still the stock recovery. My bootloader in unlocked but Secure Boot is Enabled. I think the secure boot may be why it is not flashing correctly. If so how to I disable secure boot?
jedinegotiator said:
I have used odin to flash this TAR File and it passes but when I boot into my recovery it is still the stock recovery. My bootloader in unlocked but Secure Boot is Enabled. I think the secure boot may be why it is not flashing correctly. If so how to I disable secure boot?
Click to expand...
Click to collapse
This is a known issue with TWRP even if you download the image directly. Keep rebooting to recovery it will work...eventually. I already submitted this to Team Win.
Sent from my GT-I9505G using Tapatalk 2
Updated guys 2.6.1.0 is out with new IMG and .tar files hopefully this new update fixes the freezing when we boot into TWRP I will be testing it.
Please report back on your experience.
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Updated guys 2.6.1.0 is out with new IMG and .tar files hopefully this new update fixes the freezing when we boot into TWRP I will be testing it.
Please report back on your experience.
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
If there is no difference between that .img and the one downloaded from goo.manager, Its freezing under advanced settings. Cant restore defaults. It froze on me trying to do a back up. Im sure there are several other issues as I have not had a chance to review the thread in general section yet, but just a few results from my own experience.
EDIT: I stand corrected, I thought I was getting freezes, I let it sit and it finally completed.
Hi all,
I know this is not the right area but I'm not able to post in the DEV board...
I'm using i9001 and now I'm on [ROM][JB][4.2.2][JDQ39E] CyanogenMod 10.1 by ADC Team - Release 5 - Kernel 3.4.x
I've also TWRP 2.6.0.0 Recovery on the phone because CWM has a lot of issues.
ROM and TWRP are from this page: http://forum.xda-developers.com/showthread.php?t=2315448
When I try to do a backup with TWRP my screen turns black after some time. The screen turns also black when I disable screen timeout.
Also when I'm in the main menu of TWRP screen goes black after some time.
When screen was turned off I'm not able to return to TWRP. I have to restart the phone.
Three questions:
Does anyone of you have the same issue and maybe solved that?
Does the backup fail when screen is black or is the backup finished in backgroud? Anyone knowing that or knows how to check?
Kind regards
Lukas
lok1411 said:
Hi all,
I know this is not the right area but I'm not able to post in the DEV board...
I'm using i9001 and now I'm on [ROM][JB][4.2.2][JDQ39E] CyanogenMod 10.1 by ADC Team - Release 5 - Kernel 3.4.x
I've also TWRP 2.6.0.0 Recovery on the phone because CWM has a lot of issues.
ROM and TWRP are from this page: http://forum.xda-developers.com/showthread.php?t=2315448
When I try to do a backup with TWRP my screen turns black after some time. The screen turns also black when I disable screen timeout.
Also when I'm in the main menu of TWRP screen goes black after some time.
When screen was turned off I'm not able to return to TWRP. I have to restart the phone.
Three questions:
Does anyone of you have the same issue and maybe solved that?
Does the backup fail when screen is black or is the backup finished in backgroud? Anyone knowing that or knows how to check?
Kind regards
Lukas
Click to expand...
Click to collapse
I had the same issue.
you can fix it by installing another version of twrp.
(I am not allowed to post links)
different twrp versions:
forum.xda-developers.com/showthread.php?t=2129298
Thank you!
which version are you runnung on your I9001
Then I can take the same if you are saying that this is stable
lok1411 said:
Thank you!
which version are you runnung on your I9001
Then I can take the same if you are saying that this is stable
Click to expand...
Click to collapse
my phone is flashed to stock.
I go flash the recovery and i will report you.
---------- Post added at 03:17 PM ---------- Previous post was at 02:39 PM ----------
lok1411 said:
Thank you!
which version are you runnung on your I9001
Then I can take the same if you are saying that this is stable
Click to expand...
Click to collapse
rdrai said:
my phone is flashed to stock.
I go flash the recovery and i will report you.
Click to expand...
Click to collapse
twrp 2.2.1 is stable for me.
you can download it from mediafire.
mediafire.com/download/0ufe8dcv5kkajay/twrp2.2.1-recovery.zip
please report the result back
If it worked please hit the thanks button
Hi,
thanks for your help.
some more questions regarding TWRP.
Acutally I'm running2.6.0.0
Is it possible to "downgrade" to a lower version?
Backups of 2.6.0.0 won't be used in oder versions, right?
How to deploy a downgrade? Can I just do it as an upgrad and install from zip or are there any specials.
Just replacing would work or is it a bricked version which means I have to reinstall CM10.1 and other stuff?
Last: What deffers your build from the http://forum.xda-developers.com/showthread.php?t=2129298 => TWRP => Old releases => [2.2.2.1] [1] ?
Or can this be also used?
To downgrade your recovery, just download the zip-file for twrp 2.2.1 and flash it via recovery. I don't know if your 2.6.0.0-backups will work with 2.2.1, but i would rather say no.
There shouldn't be any differences between the recovery from rdai's link and yours, you can take any of them.
Greetings, käsebr0t
Sent from my GT-I9001 using xda app-developers app
käsebr0t said:
To downgrade your recovery, just download the zip-file for twrp 2.2.1 and flash it via recovery
Click to expand...
Click to collapse
ceese! sorry chears!
You mean boot into TWRP, klick install and choose the 2.2.1 zip and install.
Or what you mean by flash via recovery.
Sorry for the stupid questions.
lok1411 said:
ceese! sorry chears!
You mean boot into TWRP, klick install and choose the 2.2.1 zip and install.
Or what you mean by flash via recovery.
Sorry for the stupid questions.
Click to expand...
Click to collapse
no thanks for me !?!
---------- Post added at 12:01 PM ---------- Previous post was at 11:25 AM ----------
lok1411 said:
ceese! sorry chears!
You mean boot into TWRP, klick install and choose the 2.2.1 zip and install.
Or what you mean by flash via recovery.
Sorry for the stupid questions.
Click to expand...
Click to collapse
twrp 2.2.1 and 2.2.2.1 are different versions, flash 2.2.1 from mediafire as i told.
Yes flash in twrp
Hi
rdrai said:
no thanks for me
Click to expand...
Click to collapse
now thanks to all for answering my stupid nerd questions!
And special thanks to rdrai for your twrp version
just installed your zip and tried to backup afterwards. Was running fine. no black screen or shutdown during backing up. Backup don within 155 secs.
Added your twrp version directly to my folder where I've stored the stable versions for CM10.1 and gaaps. Now you are also in and I have all for a pure, stalbe reset of the phone if needed.
Once more many thanks!
one more question. I added the flag "this post is a question"
Is it possible to somehow set this thread as "solved" ?
lok1411 said:
one more question. I added the flag "this post is a question"
Is it possible to somehow set this thread as "solved" ?
Click to expand...
Click to collapse
Glad to hear your problem is solved. :highfive:
i am also new on xda but i think if you add solved in the threat name then its marked as solved.
Threat title : (SOLVED) Issue with TWRP on I9001:good:
Sorry for bad english i am dutch.
I've installed the CM 10.1 to my vivid, I flashed the boot.img using fastboot usb, and installed the rom via TWRP 2.4.4.0. before any install i used the all the wipe functions im suppose too.
When it finally boots it works for like maybe a 1 sec and then reboots. What did I do wrong?
XxnubzxX said:
I've installed the CM 10.1 to my vivid, I flashed the boot.img using fastboot usb, and installed the rom via TWRP 2.4.4.0. before any install i used the all the wipe functions im suppose too.
When it finally boots it works for like maybe a 1 sec and then reboots. What did I do wrong?
Click to expand...
Click to collapse
Update: The start screen works until i select my language and press start.
XxnubzxX said:
Update: The start screen works until i select my language and press start.
Click to expand...
Click to collapse
Use wcx recovery in version 2.2 of hasoons toolkit. Wipe system, dalvik, cache, data, and do a factory reset all in wcx recovery then flash the rom then flash the correct gaps for cm10.1 or android 4.2.2 then go into the bootloader (advanced option) then flash the boot.img (fastboot flash boot boot.img)
bilibox said:
Use wcx recovery in version 2.2 of hasoons toolkit. Wipe system, dalvik, cache, data, and do a factory reset all in wcx recovery then flash the rom then flash the correct gaps for cm10.1 or android 4.2.2 then go into the bootloader (advanced option) then flash the boot.img (fastboot flash boot boot.img)
Click to expand...
Click to collapse
Still having the the issue, I took a video.
youtube(dot)com/watch?v=9RFd_FZI-1A
Too new of a member to post links.
I'll paypal anyone who can help fix this some money, amount depending on how hard the problem is.
XxnubzxX said:
Still having the the issue, I took a video.
youtube(dot)com/watch?v=9RFd_FZI-1A
Too new of a member to post links.
Click to expand...
Click to collapse
Says video is private
bilibox said:
Says video is private
Click to expand...
Click to collapse
Public now, I fixed it.
XxnubzxX said:
Public now, I fixed it.
Click to expand...
Click to collapse
Your device mobo is probably going bad and needs more power than usual to run it. Sorry. If i can get linux to boot I'll send a kernel your way to flash and see if it fixes the problem
Try overvolting the CPU, with an init.d script, that should stop it freezing up, init.d because you won't have a chance of doing it with an app
Sent from my One using xda app-developers app
In the bootloader boot a recovery if you are s-on
"fastboot boot recovery recovery.img"
Sultans thread (android12345*) his kernel thread has details on how to do it
If you are s-off just flash this. This has higher voltages. Maybe itll help ya
bilibox said:
Your device mobo is probably going bad and needs more power than usual to run it. Sorry. If i can get linux to boot I'll send a kernel your way to flash and see if it fixes the problem
Click to expand...
Click to collapse
Please send a kernal. Also, how would I flash it without S-off. Could this also cause digitizer issues? i've been seeing like a 10% line in my phones that spams touch now.
Please do I need to download any kernel to flash my HTC with cyanogenmod 10?
Sent from my HTC Velocity 4G X710s using xda app-developers app
tybaba08 said:
Please do I need to download any kernel to flash my HTC with cyanogenmod 10?
Sent from my HTC Velocity 4G X710s using xda app-developers app
Click to expand...
Click to collapse
Flash the boot.img in the rom.zip
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
XxnubzxX said:
Please send a kernal. Also, how would I flash it without S-off. Could this also cause digitizer issues? i've been seeing like a 10% line in my phones that spams touch now.
Click to expand...
Click to collapse
Last post of the first page I already attached the kernel. With a recovery.img in fastboot do "fastboot boot recovery (nameofimgfile).img" Its in android1234567's sultan kernel thread in the vivid development. all instructions are there
New to me AHD will not boot into any custom roms, I'm confused as to why. But here's what I've done:
Root (motochopper)
Unlock bootloader
Using mythtools, flashed recovery
enter recovery, factory reset, also format /system (CWM Touch 6.0.4.4)
flash CM and Gapps
Afterwards, phone just sits at boot logo. I used mythtools to reflash stock firmware, and that boots and works fine, but when I repeat the process of flashing recovery and flashing a rom, the phone will no longer boot. What am I misssing?
If you're flashing CM, make sure you flash a nightly from BEFORE July 1st, or flash milestone release M8. Then report back results.
Any CM-based ROM from after those dates won't flash because of bootloader issues related to the fact that the Atrix HD hasn't been upgraded to Motorola's latest bootloader yet.
quasihellfish said:
If you're flashing CM, make sure you flash a nightly from BEFORE July 1st, or flash milestone release M8. Then report back results.
Any CM-based ROM from after those dates won't flash because of bootloader issues related to the fact that the Atrix HD hasn't been upgraded to Motorola's latest bootloader yet.
Click to expand...
Click to collapse
Thanks. I was trying to flash M8. Guess I'm going to try and reroot and reunlock boot loader, though it's already done.
mustafu said:
Thanks. I was trying to flash M8. Guess I'm going to try and reroot and reunlock boot loader, though it's already done.
Click to expand...
Click to collapse
M8 should work. It's still JB bootloader compatible.
palmbeach05 said:
M8 should work. It's still JB bootloader compatible.
Click to expand...
Click to collapse
Same goes with validus 6.0
It's like fastboot isn't working...keep trying to flash recovery from it and it doesn't seem to work. Going to check those threads.
Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.
mustafu said:
Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.
Click to expand...
Click to collapse
Which recovery are you using?
mustafu said:
Went through the whole process again, still bootloops. rom and gapps flash fine with no errors, the only strangeness I notice is that while flashing rom in recovery, it doesn't seem to take very long (15-20 secs at most). I remember it being considerably longer, the gapps take longer to flash than the rom does. MD5 is good, rom is intact. I'm at a loss of what to do.
Click to expand...
Click to collapse
Instead of CWM Touch, try flashing Philz Advanced recovery (I think it's what most users use). Download latest from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960/
I've never had an issue using Philz. I'm on version 6.43.6 now (which is based on CWM 6.0.4.8)
bylithium said:
Which recovery are you using?
Click to expand...
Click to collapse
CWM Touch 6.0.4.4
quasihellfish said:
Instead of CWM Touch, try flashing Philz Advanced recovery (I think it's what most users use). Download latest from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960/
I've never had an issue using Philz. I'm on version 6.43.6 now (which is based on CWM 6.0.4.8)
Click to expand...
Click to collapse
Thank you, will give it a try.
mustafu said:
CWM Touch 6.0.4.4
Thank you, will give it a try.
Click to expand...
Click to collapse
I recommend philz. What rom are you flashing?
bylithium said:
I recommend philz. What rom are you flashing?
Click to expand...
Click to collapse
Was trying unified CM M8 still.
mustafu said:
Was trying unified CM M8 still.
Click to expand...
Click to collapse
How did philz go for you? I'm running sokp ?
bylithium said:
How did philz go for you? I'm running sokp ?
Click to expand...
Click to collapse
Was another no-go on PhilZ Back on Stock 4.1 again, unfortunately. Didn't even bootloop this time, just sat at the Moto logo. Strangely, I don't have the Bootloader Unlocked warning screen, just a red Moto logo, not sure how that got changed.
mustafu said:
Was another no-go on PhilZ Back on Stock 4.1 again, unfortunately. Didn't even bootloop this time, just sat at the Moto logo. Strangely, I don't have the Bootloader Unlocked warning screen, just a red Moto logo, not sure how that got changed.
Click to expand...
Click to collapse
Damn, I've messaged you.
So after a little this and that, I've realized that the md5 of the ROM isn't matching anymore, and no matter what browser and how many times I download the ROM, the md5 will now never match. Using the md5 checker on PhilZ latest. The gapps match every time when I check.
I've been using my Kingston SD card to store the ROMs and gapps, will try storing them on the phone and see how it fares.
Sent from my MB886 using Tapatalk
It's working now. Flashed the ROM, phone sat at the boot logo for 20 minutes, then the cm boot animation came on and booted from there. This is the 3rd AHD I've owned but the 1st to have this very strange behavior.
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
hello
first off cool but i think this needs to go some where else maybe wrong
sorry to be annoying i just dont want u to get yelled at if its in the wrong place
bnb25 said:
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
Click to expand...
Click to collapse
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
RockasKane said:
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
Click to expand...
Click to collapse
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
bnb25 said:
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
Click to expand...
Click to collapse
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
I did the upgrade on my device no problems GOT ROOT then had issues. After root any changes ie: install zip, backup
The unit would get stuck in recovery mode. Recoveries tried TWRP, PhilZtouch, CWM
SDcard issues were fixed with Nextapp SDfix after root
Anyone having any other issues?
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
andrewhall said:
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
Click to expand...
Click to collapse
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
no. I booted into recovery while the phone was off. 3 key Combo.
Ok, sorry to hear that.
The workaround seems to work with everybody, thats why I asked.
RockasKane said:
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
Click to expand...
Click to collapse
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
andrewhall said:
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
Click to expand...
Click to collapse
Great!
But you must thank @gr8nole... Great and hardworking guy and all the development crew that contributed with great fixes