ATTENTION EVERYONE (For everyone who attempted to install this ROM):
This ROM breaks the Tab splash screen and does harm to the Tablet.
I recommend calling 1-800-SAMSUNG, and ask for a factory re-flash. Do not say anything that you are / were rooted. This should be 100% free, they even pay for shipping. They did mine for free. I recommend doing this ASAP, before more damage might come to the Tablet.
Downloading and testing, do you need anything else? Like the twrp?
edit 1:
Impossible to install, the updater is badly configured, I can not locate the problem, even with normal recovery will not let me install, I will continue to try
edit 2:
Well I found the error, the rom is not well developed, did you do with some automated program? I remember that the tablet 10.1 has another processor and that the compatibility of a direct port without changing the drivers is impossible
jimmy999x said:
Downloading and testing, do you need anything else? Like the twrp?
edit 1:
Impossible to install, the updater is badly configured, I can not locate the problem, even with normal recovery will not let me install, I will continue to try
edit 2:
Well I found the error, the rom is not well developed, did you do with some automated program? I remember that the tablet 10.1 has another processor and that the compatibility of a direct port without changing the drivers is impossible
Click to expand...
Click to collapse
I made it on ES File Explorer, on my Nook, it took me an hour... I had ported it from Acclaim RC5 and Docker 6 Degaswifi, and I changed the updater script to say, "degaswifi", for the device. and I changed the build prop, to be the same cpu, exc... as the tab 4. I used Degaswifi Docker 6 boot.img and recovery folder, and some other important stuff in the system folder. What is the error are you getting?
secretwolf98 said:
I made it on ES File Explorer, on my Nook, it took me an hour... I had ported it from Acclaim RC5 and Docker 6 Degaswifi, and I changed the updater script to say, "degaswifi", for the device. and I changed the build prop, to be the same cpu, exc... as the tab 4. I used Degaswifi Docker 6 boot.img and recovery folder, and some other important stuff in the system folder. What is the error are you getting?
Click to expand...
Click to collapse
Even using other twrp I still can not install, use the recovery and the boot image I found 2 weeks ago, I even deleted the first line and it looked like it would install, but these errors appeared
jimmy999x said:
Even using other twrp I still can not install, use the recovery and the boot image I found 2 weeks ago, I even deleted the first line and it looked like it would install, but these errors appeared
Click to expand...
Click to collapse
Can I see what you had edited?
Only the first line of the updater inside google folder
jimmy999x said:
Only the first line of the updater inside google folder
Click to expand...
Click to collapse
What is in the first line? The new updated one, that you had did?
secretwolf98 said:
What is in the first line? The new updated one, that you had did?
Click to expand...
Click to collapse
this
jimmy999x said:
this
Click to expand...
Click to collapse
strange
I'll look into it later
jimmy999x said:
this
Click to expand...
Click to collapse
Question, after you flashed this rom, did the Splash Screen disappeared on the Samsung?
Because the both versions that I had made, broke my Samsung Splash Screen.
secretwolf98 said:
Question, after you flashed this rom, did the Splash Screen disappeared on the Samsung?
Because the both versions that I had made, broke my Samsung Splash Screen.
Click to expand...
Click to collapse
If, in fact, they stop seeing the logos of samsung when turning on and when entering the download mode, the only way to correct that is to install the official firmware
jimmy999x said:
If, in fact, they stop seeing the logos of samsung when turning on and when entering the download mode, the only way to correct that is to install the official firmware
Click to expand...
Click to collapse
so it did for you, when you flashed official PA1 firmware threw odin? did the screen that broke say, "Samsung Galaxy Tab 4 7.0 SM-T230NU Powered By Android"?
Interested to get this rom running smooth on our tabs
Related
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
riekkir said:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
Click to expand...
Click to collapse
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
es0tericcha0s said:
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
Click to expand...
Click to collapse
No I don't have it atm as I just wiped the data/cache last night but will I already have CWM, I just need to unlock the bootloader and try again...I'm trying to install this one:
Android 4.4.2 KitKat Mokee Rom, and it says the version is a nightly. Yes I'm positive it's the Bell Version as I purchased it at a Bell Store and my carrier is Bell. The error message is "Installation Aborted." It begins installing, and then halfway through I get that error message. How do I fix this?
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960
es0tericcha0s said:
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
Click to expand...
Click to collapse
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
riekkir said:
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
Click to expand...
Click to collapse
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
http://forum.xda-developers.com/showthread.php?t=2619489
For installing recovery:
http://forum.xda-developers.com/showthread.php?t=2262726
es0tericcha0s said:
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
For installing recovery:
Click to expand...
Click to collapse
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
riekkir said:
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
Click to expand...
Click to collapse
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
es0tericcha0s said:
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
Click to expand...
Click to collapse
Okay so I'm trying it now and the program won't even open :/
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
es0tericcha0s said:
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
Click to expand...
Click to collapse
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
riekkir said:
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
Click to expand...
Click to collapse
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
es0tericcha0s said:
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
Click to expand...
Click to collapse
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
riekkir said:
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
Click to expand...
Click to collapse
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
es0tericcha0s said:
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
Click to expand...
Click to collapse
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
riekkir said:
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
Click to expand...
Click to collapse
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
es0tericcha0s said:
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
Click to expand...
Click to collapse
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
riekkir said:
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
Click to expand...
Click to collapse
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
es0tericcha0s said:
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
Click to expand...
Click to collapse
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
riekkir said:
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
Click to expand...
Click to collapse
Oh yea, forgot you have to undo the screws on the bottom. So you scroll down to hit recovery and use the Power button to select and it doesn't do anything? That's odd.. Try and reflash the recovery since you can still get to fastboot. If that doesn't work, you're not totally screwed since you can still get to fastboot, that means you should be able to restore it to stock and start over.
Alternatively, if you have fastboot set up, you could make sure that philz touch is in the fastboot folder and use this command:
fastboot boot recovery nameofphilztouchfile.img
If you don't have fastboot, then just grab this one: http://forum.xda-developers.com/showthread.php?t=2317790 , drop the recovery img in that folder and open the CMD prompt on your computer and change directories to it and run the command.
Download
Mega
Installing
You can't flash this yet (I'm working on that, I promise) but you can boot from it!
NOTE: THIS IS A WIP. Not a lot has been really tested yet and this is posted merely for your enjoyment atm.
I don't suggest flashing anything yet, not that there is anything to flash heh.
Also, I take no responsibility if you break your watch, yada, yada.
To do this, make sure you have Android's tools (for fastboot), an unlocked bootloader, and the watch connected to your computer in Debug mode.
> adb reboot bootloader
<wait for the reboot to happen>
> fastboot boot /path/to/recovery.img
Click to expand...
Click to collapse
Enjoy!
Did u push the tree to github?
1st built for me was a no go
wouldn't twrp make more sense since its touch based?
D-FUSE said:
Did u push the tree to github?
1st built for me was a no go
Click to expand...
Click to collapse
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
ptesmoke said:
wouldn't twrp make more sense since its touch based?
Click to expand...
Click to collapse
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
ptesmoke said:
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
Click to expand...
Click to collapse
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
dude1981 said:
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
jamcar said:
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Click to expand...
Click to collapse
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Click to expand...
Click to collapse
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Click to expand...
Click to collapse
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
PlayfulGod said:
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Click to expand...
Click to collapse
It's only booting because it doesn't work when flashed to recovery. The file size is around 8 mb whereas the legitimate recovery is 23 mb, which I'm sure is an issue. Is it possible that I'm only creating a ramdisk that gets paired with the watch's kernel and I need to make an image with both of them? Sorry, this whole uBoot stuff confuses me a bit.
PlayfulGod said:
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Click to expand...
Click to collapse
Heh, I'm not actually afraid of git, I guess, I'm afraid of the whole "making a device-specific git repo that can be easily pulled while building CM." I guess I just don't have the time atm to set it up properly, but dw, I'll get to it this weekend! :fingers-crossed:
dude1981 said:
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, the iOS mod is something I downloaded awhile ago for my N5. I'm afraid I don't have the link anymore. Sorry, man.
Pepski said:
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
Click to expand...
Click to collapse
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Smith7018 said:
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Click to expand...
Click to collapse
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Pepski said:
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Click to expand...
Click to collapse
Weird... I don't even think you need root to push to /sdcard/ but I could be wrong. I'd suggest trying /sdcard/emoji.zip so it knows where to resolve. Also, I don't use Windows, but does the backslash work on adb as a file separator?
what happened to development on this?
Help! I made the foolish decision to try and mess around in my G3's build.prop without really knowing what I was doing. My phone is currently stuck in a bootloop, not getting past the verizon splash screen. I have attempted booting into recovery mode and factory resetting, but for one reason or another, the phone won't do it and it ends up loading the splash screen over and over again. I have also researched flashing the stock rom onto the device with the LG flash tool. But, when I try to do this, the tool gives me an error saying that the "Device Model is different" because according to the build.prop, it is a Nexus 5.
Does anyone know of a method that can help me get this stupid thing working again?
I have seen build.prop files cut in half because it was a bad file editor. I hope u saved a copy. Posible reboot to fast boot and replace? Rom toolbox has nice interface for editing build.prop.
Sent from my VS985 4G
Thanks for your reply! I do have a copy. How would I go about booting into fast boot?
n8bgr8 said:
Thanks for your reply! I do have a copy. How would I go about booting into fast boot?
Click to expand...
Click to collapse
what do you have in the recovery partion, stock or or bumped twrp?
Well, I fixed it somehow. I got the stock Rom to flash, but I don't really,understand what,made it work this time. Whatever, I've learned my lesson. Thank you for your attempt to help!
n8bgr8 said:
Well, I fixed it somehow. I got the stock Rom to flash, but I don't really,understand what,made it work this time. Whatever, I've learned my lesson. Thank you for your attempt to help!
Click to expand...
Click to collapse
Cool. I was going to mention that their may be a force or overide in the lg flashing software. Manual was one of the was to flash. any input you can add on how you did it would be great as I have read people have run into this before. their is no need to change the phone type to download apps from the market that are not compatible with your phone. The following link allows you to download any app and then you can sideload it (for future reference)
http://apps.evozi.com/apk-downloader/?id=ca.halsafar.genesisdroid
usage. go to the link. replace [ca.halsafar.genesisdroid] in your browser with the app you looking to download from the play store using the ending link in the play store address. then click the blue generate button on the page. a new green button to download the file will appear.
glad it worked out for ya. And check out rom tool boxs build.prop editor. very nice.
Hi Internet,
I was trying to flash Android M on my Nexus 9 (Wi-Fi only) today and ended up with errors such as: "system.ui has stopped working" or "android.process has stopped" because I wanted to see if I actually needed to do a factory reset for it to work properly (turns out I do). After that I've tried again and have run into some issues.
Firstly, after that Android M wasn't flashing at all and I have decided to abandon the idea of M and just go back to Lollipop. Now, I am trying to flash 5.1.1 and I keep on getting FAILED (remote: data length is too large) error when flashing my system partition. I'm flashing everything separately because if I try to do it as one image because I keep getting error: update package missing system.img errors. I have no trouble with flashing my bootloader and other partitions(boot, cache, recovery, etc), but that system partition just won't flash! I've tried 5.0, 5.1, 5.1.1 and I keep on getting these errors.
I have no idea what to do. Please help. I've spent the last 5 hours trying to figure it out and nothing has yet came up. I'm using a Mac, but I don't see how this might be causing an issue.
If you have any valuable information - please help!
I'm very comfortable with flashing and ROMs, in fact I've updated my N5 to M in 5 min, but I've never seen this error before and have no idea how to fix. All I found out is that, I think, it only happens on HTCs...
Solved: http://forum.xda-developers.com/showpost.php?p=61354553&postcount=14
I can't help you but I can tell you I had the same problem. After much frustration and many attempts to flash 5.1.1 it finally worked. I was ready to rma the device as I was sure something was wrong with it. Sorry I can't be more help as getting it to work was so random.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I can't help you but I can tell you I had the same problem. After much frustration and many attempts to flash 5.1.1 it finally worked. I was ready to rma the device as I was sure something was wrong with it. Sorry I can't be more help as getting it to work was so random.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Did you by any chance use any special image or was it a normal image from Google?
tarasmuz said:
Did you by any chance use any special image or was it a normal image from Google?
Click to expand...
Click to collapse
No,I used the factory image from Google. There were a number of times I got the image to flash, I flashed images separately, but got boot loops even after factory resets. Even got it to boot a couple of times but couldn't sign into Google. Wi-Fi would keep resetting and bring me back to the Google sign in. I'm still not convinced that there isn't something wrong with the device, bad nand? But it's working now. I haven't tried to flash anything since.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
No,I used the factory image from Google. There were a number of times I got the image to flash, I flashed images separately, but got boot loops even after factory resets. Even got it to boot a couple of times but couldn't sign into Google. Wi-Fi would keep resetting and bring me back to the Google sign in. I'm still not convinced that there isn't something wrong with the device, bad nand? But it's working now. I haven't tried to flash anything since.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm pretty sure that the device is fine. I flashed images before and had no problems at all.
If you haven't already, make sure nothing is running in the back ground on your pc that might be using ram. The complete system image has to load into ram and it's a pretty big file.
jd1639 said:
If you haven't already, make sure nothing is running in the back ground on your pc that might be using ram. The complete system image has to load into ram and it's a pretty big file.
Click to expand...
Click to collapse
I've just restarted and closed all the programs, but it didn't help. Going to be trying and will post if I manage to make it work. Thanks for your help!
You might have already tried this too, but re-download the factory image, check it's md5, then extract it. Might be a bad download or extraction. Then follow the long method in this, http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
jd1639 said:
You might have already tried this too, but re-download the factory image, check it's md5, then extract it. Might be a bad download or extraction. Then follow the long method in this, http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Yeah, I've tried all of that. Also checked MD5 and it matches to the one on the website. The only thing I could think of is bad extraction. Will try another unarchiver.
tarasmuz said:
Yeah, I've tried all of that. Also checked MD5 and it matches to the one on the website. The only thing I could think of is bad extraction. Will try another unarchiver.
Click to expand...
Click to collapse
Just tried another unarchiver - no difference.
tarasmuz said:
Just tried another unarchiver - no difference.
Click to expand...
Click to collapse
What are you using? Use winrar or 7-zip
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
What are you using? Use winrar or 7-zip
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I'm on a Mac, so The Unarchiver and Archive Utility.
tarasmuz said:
Hi Internet,
I was trying to flash Android M on my Nexus 9 (Wi-Fi only) today and ended up with errors such as: "system.ui has stopped working" or "android.process has stopped" because I wanted to see if I actually needed to do a factory reset for it to work properly (turns out I do). After that I've tried again and have run into some issues.
Firstly, after that Android M wasn't flashing at all and I have decided to abandon the idea of M and just go back to Lollipop. Now, I am trying to flash 5.1.1 and I keep on getting FAILED (remote: data length is too large) error when flashing my system partition. I'm flashing everything separately because if I try to do it as one image because I keep getting error: update package missing system.img errors. I have no trouble with flashing my bootloader and other partitions(boot, cache, recovery, etc), but that system partition just won't flash! I've tried 5.0, 5.1, 5.1.1 and I keep on getting these errors.
I have no idea what to do. Please help. I've spent the last 5 hours trying to figure it out and nothing has yet came up. I'm using a Mac, but I don't see how this might be causing an issue.
If you have any valuable information - please help!
I'm very comfortable with flashing and ROMs, in fact I've updated my N5 to M in 5 min, but I've never seen this error before and have no idea how to fix. All I found out is that, I think, it only happens on HTCs...
Click to expand...
Click to collapse
Your Android SDK (fastboot) probably needs to be updated. Depending on how old it is, Google updated the SDK and fastboot to allow flashing these very large system.img files in early November, 2014.
cam30era said:
Your Android SDK (fastboot) probably needs to be updated. Depending on how old it is, Google updated the SDK and fastboot to allow flashing these very large system.img files in early November, 2014.
Click to expand...
Click to collapse
Yes! It worked! Turns out I was using this outdated fastboot file which wasn't allowing flashing newer system partitions. Fun fact: outdated fastboot file worked with N5, but didn't work with N9. Anyway, I updated my SDK though Android Studio and everything flashed perfectly. Many thanks to cam30era and jd1639.
tarasmuz said:
Yes! It worked! Turns out I was using this outdated fastboot file which wasn't allowing flashing newer system partitions. Fun fact: outdated fastboot file worked with N5, but didn't work with N9. Anyway, I updated my SDK though Android Studio and everything flashed perfectly. Many thanks to cam30era and jd1639.
Click to expand...
Click to collapse
I'm glad this worked out for you.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Features:
-touchwiz ui with near stock functionality
-based on Tab A and Tab S frameworks
-Tab S2 apps
-Tab S3 UI Sounds
-SPen features
-theme support
-pre-rooted (magisk)
-deodexed
-debloated
-knox removed
-all apps support multiwindow
-some minor changes like removing safe volume warning, overlay fix etc
-ported IronKernel from @Tkkg1994 (read more about kernel features here: https://forum.xda-developers.com/galaxy-tab-s/orig-development/kernel-ironstock-kernel-v3-2-t3531295 )
Notes:
full wipe required!
First boot takes 10 minutes
For some features root required
Device encryption doesn't support here
If you don't want to install root, remove magisk folder from install zip
If you don't have working spen, flash stock rom before this one.
If you want to make custom rom based on my rom, you're welcome.
Thanks to @Miron24 for testing rom
Download:
02feb
gdrive: https://drive.google.com/open?id=1sAiyxBEkEDEWtOiuMvOM53DKWmAVWHQx
Thanks to @Tkkg1994 for the kernel
Kernel sources:
https://github.com/bonuzzz/IronKernel
I'll download and give this a shot. I really need all apps in multi windows.
How works SPEN?
write me please your feedback, what working or not working in hardware part
won't work on p600,
@maxximboy black screen after bootloader without any reboots?
@bonuzzz
Do your roms (P900, P600, T900) work on 3G devices(P901, etc.)? I want to test your rom on my P601. Do you plan to port Tab A 10.1 with S Pen apps to your roms?
Miron24 said:
@bonuzzz
Do your roms (P900, P600, T900) work on 3G devices(P901, etc.)? I want to test your rom on my P601. Do you plan to port Tab A 10.1 with S Pen apps to your roms?
Click to expand...
Click to collapse
if you dont need 3g support, so it should working. but current version doesn't boot on p600. trying to find, where is problem in kernel. wait for fix.
do you want exact app from tab A ?
Hi there, good to see this kind of development. I tried flashing, but install was unsuccessful.
Previous ROM is Resurrection Remix for P600
Went to recovery, did factory reset on TWRP, then wiped System partition
Flashed your zip, and out comes on the terminal:
This package is for "v1awifi, v2awifi, n1awifi, n2awifi, klimtwifi, chagallwifi" devices, this is a "lt03wifiue"
Updater process ended with ERROR: 7
So I assume the problem lies somewhere with the device name/code, but I'm not sure how to change this. From what I've searched it's in build.prop, but that doesn't exist one /system is wiped. After wiping everything I tried flashing AICP Rom, but still the same error code comes out when I tried flashing your .zip. Have any other tips? I assume you also have a P600 no? How did you get it to boot?
EDIT: Thanks for correcting noob mistake @mosimchah
Pact said:
Previous ROM is Resurrection Remix for P600 ie AOSP based
Click to expand...
Click to collapse
Resurrection Remix is lineage based, and lineage is caf based (not AOSP)
Sent from my LEX727 using XDA Labs
---------- Post added at 06:07 PM ---------- Previous post was at 06:00 PM ----------
bonuzzz said:
if you dont need 3g support, so it should working. but current version doesn't boot on p600. trying to find, where is problem in kernel. wait for fix.
do you want exact app from tab A ?
Click to expand...
Click to collapse
Check out the unofficial Lineage 13.0 kernel, it's based on the tab s mm source and works on the p600
https://github.com/exynos5420/andro...configs/cyanogenmod_deathly_n1awifi_defconfig
https://github.com/exynos5420/andro...tree/091b5954799bbfbb38bced4ac6342c5939900348
Sent from my LEX727 using XDA Labs
ok, lt03wifiue is also p600. I didn't know that. you could remove assert in updater-script to disable check device.
@Pact I have P900
OK, I removed the assert lines as per this guide:
https://forum.xda-developers.com/showpost.php?p=31519426&postcount=186
Used 7zip, edited the file mentioned above, deleted the lines, 7zip recompiles that, moved it to SD card and started flashing. Of course I did a factory reset beforehand, and wiped /system too. The usual stuff appears:
Checking config . . .
Formatting system . . .
Extracting system . . .
The flash was successful, then the Magisk installation lines appear and that was good too.
Once that's done, I flashed the kernel provided above, and that complete, I rebooted the tablet, no other warnings or anything like that appearing during installation. The Galaxy Note screen appeared, then the screen went black (lights on, nothing else displayed). I thought this was normal for a new flash, then I waited till 20 minutes and it's still like that. So I forced a reboot (long press power button) and the Galaxy Note screen appeared again, this time I've waited 5 minutes and nothing else happens - still lighted screen with nothing else. The backside is hot during both reboots, so something is definitely happening using CPU cycles, but I'm not sure what. Should I dirty reflash next?
bonuzzz said:
ok, lt03wifiue is also p600. I didn't know that. you could remove assert in updater-script to disable check device.
Test please this kernel
https://yadi.sk/d/WGxcpVrn3K6G7R
@Pact I have P900
Click to expand...
Click to collapse
Make sure you're using the proper vendor blobs
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/n1awifi
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/nx-common
https://github.com/exynos5420/proprietary_vendor_samsung/tree/cm-13.0/exynos5420-common
Using the tab s blobs could cause it to not boot
Pact said:
OK, I removed the assert lines as per this guide:
https://forum.xda-developers.com/showpost.php?p=31519426&postcount=186
Used 7zip, edited the file mentioned above, deleted the lines, 7zip recompiles that, moved it to SD card and started flashing. Of course I did a factory reset beforehand, and wiped /system too. The usual stuff appears:
Checking config . . .
Formatting system . . .
Extracting system . . .
The flash was successful, then the Magisk installation lines appear and that was good too.
Once that's done, I flashed the kernel provided above, and that complete, I rebooted the tablet, no other warnings or anything like that appearing during installation. The Galaxy Note screen appeared, then the screen went black (lights on, nothing else displayed). I thought this was normal for a new flash, then I waited till 20 minutes and it's still like that. So I forced a reboot (long press power button) and the Galaxy Note screen appeared again, this time I've waited 5 minutes and nothing else happens - still lighted screen with nothing else. The backside is hot during both reboots, so something is definitely happening using CPU cycles, but I'm not sure what. Should I dirty reflash next?
Click to expand...
Click to collapse
Sent from my LEX727 using XDA Labs
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
bonuzzz said:
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
Click to expand...
Click to collapse
I'm not using this ROM, just happened to see the thread
Sent from my LEX727 using XDA Labs
bonuzzz said:
@maxximboy black screen after bootloader without any reboots?
Click to expand...
Click to collapse
no no black or blank screen, it wont flash the rom, message was something like, my p600 is not compatible.
View attachment tombstones.zip
View attachment last_kmsg.txt
bonuzzz said:
@mosimchah if you have p600, send me please last_kmsg and tombstones. it will help me a lot
it's not vendor. it should be kernel or init scripts. or i miss something.. without log it's difficult to guess
Click to expand...
Click to collapse
Hre's those files. After the second black blank screen that I mentioned in my previous post, I rebooted to recovery and grabbed these from the file manager. There's 10 tombstone files in the folder so I zipped it up. Hope it helps.
I am really excited about this rom, and cant wait to flash it on my p600..... i am not techies as you guys, so my question is, what do i need to do to make it work?
thanks all
maxximboy said:
I am really excited about this rom, and cant wait to flash it on my p600..... i am not techies as you guys, so my question is, what do i need to do to make it work?
thanks all
Click to expand...
Click to collapse
It need proper kernel ...patience
I need a tester, who will spend some time to flash couple of builds. write in pm
thanks in advance