Hi,
I want to try install the new Cyanogenmod on my Tab, read a bit about it, and tried last night to get it going. many different forums and steps were tried... none worked? Thing is, I read a lot of terms and stuff, but I'm not sure what they all mean.
My route took me through Android SDK's for drivers, Samsung drivers with escape??? no clue what that was?? Nvidia drivers? Then tried to use a program called Clockworkmod? Confusing, especially since nothing seemed to actually do anything?
What is it that I need to do exactly?
What i can say is that when I boot my Tab up, there is an unlocked padlock at the bottom of the screen.
I have the latest Cyanogenmod for my Tab "p3" downloaded, as well as the Google Apps.
Cheers
Weevil Kneevil said:
Hi,
I want to try install the new Cyanogenmod on my Tab, read a bit about it, and tried last night to get it going. many different forums and steps were tried... none worked? Thing is, I read a lot of terms and stuff, but I'm not sure what they all mean.
My route took me through Android SDK's for drivers, Samsung drivers with escape??? no clue what that was?? Nvidia drivers? Then tried to use a program called Clockworkmod? Confusing, especially since nothing seemed to actually do anything?
What is it that I need to do exactly?
What i can say is that when I boot my Tab up, there is an unlocked padlock at the bottom of the screen.
I have the latest Cyanogenmod for my Tab "p3" downloaded, as well as the Google Apps.
Cheers
Click to expand...
Click to collapse
You need to use Odin to flash Clockworkmod recovery onto your tablet.
Then you need to download the p4wifi (if yours is wifi) edition of CM9
Then boot clockworkmod recovery and flash CM9 and then Google Apps
ok, but with more in depth steps please, i got a better idea now though!! thanks
Weevil Kneevil said:
ok, but with more in depth steps please, i got a better idea now though!! thanks
Click to expand...
Click to collapse
Root http://www.androidauthority.com/galaxy-tab-10-1-root-clockworkmod-recovery-50799/ (stop after step 12.)
CM9 Flashable Zip http://download.cyanogenmod.com/get/jenkins/4709/cm-9-20120720-NIGHTLY-p4wifi.zip
Get into recovery mode, go to install zip from SD, select the zip /\ hit yes. Reboot.
Ok, no joy,
What I seem to have:
A working fastboot, fastboot devices does list my device. And when I try flash something via Odin, my Tab says "flashing mbr to device" so my action on my pc does initiate something on the tab. yet it stops there, at the flashing mbr to device screen. It does not start the recovery img.
A working adb, adb reboot recovery does reboot my tablet, but it still does not boot into recovery. It has a android sign, with a yellow exlamation mark over it.
I've tried to flash skitzandroid, clockworkmod, and the tabrooteasy one. I just cant seem to get this thing rooted?
Is there something I'm missing?
I do have an unlocked padlock on my screen when i boot it up.
He has a p7100 why are you guys sending him to flash p4wifi Wtf!
Dude go to 10.1v development section and read cm9 thread you will find everything you need there
Sent from my GT-N7000 using xda premium
msedek said:
He has a p7100 why are you guys sending him to flash p4wifi Wtf!
Click to expand...
Click to collapse
I had a good laugh about that one too But hey, all the clues I got, got me on the right trail!
I got it sorted! Thanks for the help guys!!
Cheers!
Related
Hey guys,
I've been searching for an answer for days now and I finally decided to make an account here on XDA.
I recently unlocked the bootloader of my Atrix (I have superuser and all) and now I want to upload a custom ROM (CM7). I followed the steps on the CM7 thread for installation yet I was left scratching my head and eventually was extremely frustrated after many reboots, configurations, and even a hard reset!
I used ROM Manager to get CWM, I flashed the latest version, and entered recovery mod, both from the app and manually. Nothing - just the Android Recovery. Tried many times, sometimes I was given a "failed to boot 2, starting RSD mode" error but most of the times I was just taken to the normal recovery.
I read somewhere that the install-recovery.sh file found in the system had to be deleted so I downloaded ES File Explorer, enabled root and writing and successfully deleted it (or so I thought), I was taken to the android recovery again! When I checked the file explorer again, install-recovery.sh was back... I have tried many times and it keeps on returning.
What am I doing wrong? I don't even know how to use fastboot, I am a noob and 90% of the language used on this forum is foreign to me hahaha (I traded my iPhone 4 for the Atrix less than two weeks ago). Also, I accidentally deleted my install-recovery.sh.bak file, is that important?
Any help would be appreciated.
Thanks,
Kevin.
Alright, calm down, and dont panic, I was a noob too, just dont do anything rash and this'll be fine. First off, the install-recovery.sh.bak thing, or whatever you said it was called, is just a backup of whatever it was replacing, hence the .bak file extension. Now, you can still get into Android right, everything boots correctly and whatnot, or are you not able to boot right now? Also, it says youre unlocked for sure, correct? Like, when you boot, it says Unlocked up in the corner? We're going to get you through this, just answer these questions first
Hey,
Sorry if I sounded dramatic haha, just typed off the top of my head.
Thanks for clarifying regarding the bak file. No, it does not say unlocked at the top corner when booting, i assumed having the superuser app meant that I was unlocked/bootloader unlocked. The am I missing something here?
Also, my phone is totally functional. In fact, I am typing this on it
Killer0Kevin said:
Hey,
Sorry if I sounded dramatic haha, just typed off the top of my head.
Thanks for clarifying regarding the bak file. No, it does not say unlocked at the top corner when booting, i assumed having the superuser app meant that I was unlocked/bootloader unlocked. The am I missing something here?
Click to expand...
Click to collapse
Yeah, your not unlocked at all... maybe rooted, but not unlocked. See my signature for noob guide.
Sent from my MB860 using xda premium
I have been trying all day to unlock the bootloader with no success lol
I can't install RSDlite, it gives me error 29** or something like that, have tried multiple download links and I cannot install the x64 driver, my desktop is running 32 bit which is probably the issue I'm guessing... Any alternates? It gives me a "processor type not compatible" error.
Killer0Kevin said:
I have been trying all day to unlock the bootloader with no success lol
I can't install RSDlite, it gives me error 29** or something like that, have tried multiple download links and I cannot install the x64 driver, my desktop is running 32 bit which is probably the issue I'm guessing... Any alternates? It gives me a "processor type not compatible" error.
Click to expand...
Click to collapse
Have you tried the automatic unlock linked to in Swift's N00B guide? It doesn't get any easier than that.
It's packaged with RSDLite 5.3.1. It's the one I used to unlock. Don't see why it wouldn't still work. There's a link to Motorola's driver page there as well.
Do not use the CWM packaged with it though, it's outdated. Flash romracer's or ROM Manager's.
ghost_og said:
Have you tried the automatic unlock linked to in Swift's N00B guide? It doesn't get any easier than that.
It's packaged with RSDLite 5.3.1. It's the one I used to unlock. Don't see why it wouldn't still work. There's a link to Motorola's driver page there as well.
Do not use the CWM packaged with it though, it's outdated. Flash romracer's or ROM Manager's.
Click to expand...
Click to collapse
Yes I have.
I followed all the steps and eventually it got to the unique ID part, no ID was shown, googled it and found out that I had to use RSDlite first, but there's my problem.. Also tried the fastboot oem method, same problem.
Killer0Kevin said:
Yes I have.
I followed all the steps and eventually it got to the unique ID part, no ID was shown, googled it and found out that I had to use RSDlite first, but there's my problem.. Also tried the fastboot oem method, same problem.
Click to expand...
Click to collapse
You had mentioned you were trying to use the x64 drivers on a 32-bit machine. Did you ever get around to installing the correct x86 ones from the Motorola site?
ghost_og said:
You had mentioned you were trying to use the x64 drivers on a 32-bit machine. Did you ever get around to installing the correct x86 ones from the Motorola site?
Click to expand...
Click to collapse
No, I have not. Would you find sending me the link? I don't know where to start haha
I will try on my other desktop later after I finish my homework
Killer0Kevin said:
No, I have not. Would you find sending me the link? I don't know where to start haha
I will try on my other desktop later after I finish my homework
Click to expand...
Click to collapse
See my previous post, #7. If you go to that automatic unlock thread, there is a link to the Motorola drivers page in the instructions. Look at the prerequisites.
Got it working, thanks guys!
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
neonblur said:
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
Click to expand...
Click to collapse
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
neonblur said:
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
Click to expand...
Click to collapse
yea that inf file is the one you need to modify. but you already have adb composite interface... so that means drivers are installed.
what happens when you do adb devices after you get into cwm. what's the output?
Sent from my Nook Tablet CM7 BETA using xda premium app
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
neonblur said:
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
Click to expand...
Click to collapse
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
neonblur said:
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
Click to expand...
Click to collapse
ok well now you have adb working. now the problem is how to fix your problem lol... I'll see if I can think of something.
in the meantime can you go into detail as to how you got tto your current situation?
EDIT: do you get any errors when booting into cwm? like not being able to mount a certain drive or something?
Sent from my Nook Tablet CM7 BETA using xda premium app
no errors booting into cwm internal and never had a problem when booting into it from an sd card. i flashed it internally hoping it would be a little easier seeing as how i only have one sd card but i am going to go get another today just to work through this.
nook started on 1.4.3 i rooted it using brianf23 and indirects sd card method. market and everything worked great. so i flashed Veronica's CM7beta_ribbon_ICS rom. everything for the most part was working, tho i did notice that some menu items would not open for me but they were noting i really needed to mess with at the time. so i installed a few apps and was done for the day. turned it on the next day and got stuck in a bootloop, so powered off and rebooted but got the same bootloop. booted into recovery did the standard dalvik cache ect and reflashed the rom, hoping this might fix the loop. upon rebooting is when i got stuck at the 'please reboot your device' screen. i have tried several methods of just flashing to stock ect, formatted my sd correctly and made sure it was active to try and flash back to stock that way but my nook will not boot from sd. so 12+ hours later i hung my head and asked for help lol! thanks to you i am able to start ADB no clue what to do but hey....step in the right direction!
Happy Dance
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
neonblur said:
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
Click to expand...
Click to collapse
good job on the fix. glad to help
Sent from my Nook Tablet CM7 BETA using xda premium app
Hello all,
I could not find a solution to my question anywhere. I tried searching, and no luck. I'm hoping one of you really smart devs can help me figure this out.
Ok here goes
1. I was trying to root my mp3 player for a while, a Galaxy Player 3.6 US version (capacitive button)
2. Using the steps at this guide, and the rom from this guide
3. Everything was working perfectly until i tried starting up after i had finished with Odin. As it booted up, I saw that it had a discolored and messed up screen, as in everything was yellow and garbled
4. When i finally got past it having a black screen after that, I saw that it was way screwed up. The screen resolution was way too large, and I couldn't do anything
5. When i tried to re flash the phone to the original stock rom, I tried going into download mode and Odin did not recognize the device, and neither did windows. When I turn it on, and let it boot into the screwed up resolution, It works to a certain extent, as i can open ADB, the drivers working. When i tried using adb push sysbkup (my backup dir from before the root) /sdcard/system (the system directory), nothing happened.
6. This mp3 player is what I need everyday, so I really need help fixing it. Just for the record, Odin does not see the device when it is in download mode, so I cannot re flash it to the original stock rom D:
Thanks for any help, appreciate it
The player actually starts up, but I cannot log in, and It won't show the entire number pad. Adb only recognizes the device when it is actually turned on and booted up into android.
If anyone could help, It's greatly appreciated
shadowblade2652 said:
Hello all,
I could not find a solution to my question anywhere. I tried searching, and no luck. I'm hoping one of you really smart devs can help me figure this out.
Ok here goes
1. I was trying to root my mp3 player for a while, a Galaxy Player 3.6 US version (capacitive button)
2. Using the steps at this guide, and the rom from this guide
3. Everything was working perfectly until i tried starting up after i had finished with Odin. As it booted up, I saw that it had a discolored and messed up screen, as in everything was yellow and garbled
4. When i finally got past it having a black screen after that, I saw that it was way screwed up. The screen resolution was way too large, and I couldn't do anything
5. When i tried to re flash the phone to the original stock rom, I tried going into download mode and Odin did not recognize the device, and neither did windows. When I turn it on, and let it boot into the screwed up resolution, It works to a certain extent, as i can open ADB, the drivers working. When i tried using adb push sysbkup (my backup dir from before the root) /sdcard/system (the system directory), nothing happened.
6. This mp3 player is what I need everyday, so I really need help fixing it. Just for the record, Odin does not see the device when it is in download mode, so I cannot re flash it to the original stock rom D:
Thanks for any help, appreciate it
The player actually starts up, but I cannot log in, and It won't show the entire number pad. Adb only recognizes the device when it is actually turned on and booted up into android.
If anyone could help, It's greatly appreciated
Click to expand...
Click to collapse
I think if you can enter in download mode you flash the 3.6 US rom from my topic : http://forum.xda-developers.com/showthread.php?t=1864741
Rom is a Linux Kernel and Android system : The kernel must be compiled for every device because he have driver and some feature for this unique device. The Android system can run can run with another device like freexperia rom for sony. 3.6, 4.0, 4.2, 5.0 device are different.
Quentinga said:
I think if you can enter in download mode you flash the 3.6 US rom from my topic : http://forum.xda-developers.com/showthread.php?t=1864741
Rom is a Linux Kernel and Android system : The kernel must be compiled for every device because he have driver and some feature for this unique device. The Android system can run can run with another device like freexperia rom for sony. 3.6, 4.0, 4.2, 5.0 device are different.
Click to expand...
Click to collapse
I can enter download mode, That isn't the problem. The problem is that i can't connect it to my computer , my computer won't recognize my mp3
Also, I have tried new drivers, but Odin only detects it while it's actually on (android)
Edit:
Windows update is so useful! It downloaded the CORRECT drivers, so now im able to reflash to the stock rom. Any ideas of how to root it correctly? I don't want to screw it up again
I reflashed the stock rom, and now it STILL doesn't work???
It is still having that discolored startup and the resolution problem
shadowblade2652 said:
I can enter download mode, That isn't the problem. The problem is that i can't connect it to my computer , my computer won't recognize my mp3
Also, I have tried new drivers, but Odin only detects it while it's actually on (android)
Click to expand...
Click to collapse
This is a really weird problem, because when i go into download mode, it still says that im running the official samsung rom, so I'm wondering if it even flashed correctly?
Now it says custom, even when i download the stock rom? Is there something wrong? I do NOT want to root it if i can't use my mp3, and the main problem of using it after trying to root is that the screen res changes, and I'm only able to see the top half of the screen
Quentinga said:
I think if you can enter in download mode you flash the 3.6 US rom from my topic : http://forum.xda-developers.com/showthread.php?t=1864741
Rom is a Linux Kernel and Android system : The kernel must be compiled for every device because he have driver and some feature for this unique device. The Android system can run can run with another device like freexperia rom for sony. 3.6, 4.0, 4.2, 5.0 device are different.
Click to expand...
Click to collapse
Can you provide me with an actual stock rom from anywhere? I can't find one, they are all rooted and I need a regular, stock, unrooted rom :S
I tried unrooting with a rom i thought was "stock" but it still says custom rom in download mode, and I haven't seen anything except once i tried to flash and it gave me a yellow triangle. The system boots up into the screwed up verson,
I also cannot clear my caches as recovery mode won't let me select anything because the home button doesn't work, and neither does the screen or anything for that matter. The screen does not register touches
Ok i tried something new and just flashed the stock INT version
The system starts up in the correct resolution but it doesn't register touches still
Ok, so I managed to get the correct rom installed, everything looks normal except for one thing. The touchscreen does not work. Does anyone have ANY idea how to fix this?
shadowblade2652 said:
Ok, so I managed to get the correct rom installed, everything looks normal except for one thing. The touchscreen does not work. Does anyone have ANY idea how to fix this?
Click to expand...
Click to collapse
What you want to do is start clean by deleting the drivers for the gplayer 3.6 and reinstalling them, then plug in your player and make sure Odin can detect it, then flash the appropriate ROM. this whole thing could have been from a bad cable or driver, make sure you have the USA ROM because the international does not have the same kernel.
Work Smarter, Not Harder
Sparx639 said:
this whole thing could have been from a bad cable or driver
Click to expand...
Click to collapse
Actually he has been posting in many of the 3.6 threads. His problem was caused by flashing 4.2 ROM to his 3.6 device, which seems to have overwritten more than just his kernel and system. He always seems to leave that part out In hopes that someone actually can fix his problem without understanding it
Sent from my SGH-I777 using xda app-developers app
krzee said:
Actually he has been posting in many of the 3.6 threads. His problem was caused by flashing 4.2 ROM to his 3.6 device, which seems to have overwritten more than just his kernel and system. He always seems to leave that part out In hopes that someone actually can fix his problem without understanding it
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
I actually didn't leave that out because what happened was I didn't realize that i had flashed the incorrect rom...
Is there anyway i can get the drivers for the touchscreen? Maybe reinstall them?
krzee said:
Actually he has been posting in many of the 3.6 threads. His problem was caused by flashing 4.2 ROM to his 3.6 device, which seems to have overwritten more than just his kernel and system. He always seems to leave that part out In hopes that someone actually can fix his problem without understanding it
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Oh lol
Sent from my Galaxy Nexus using xda premium
Sparx639 said:
Oh lol
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
"Leaving out that part in hopes" <------ is actually because i haven't looked on this thread since i found out what i had done wrong...
(oh btw, how do i get my gp3.6 out of recovery mode because when i used adb i typed reboot recovery and so it only boots recovery)
[Q] Can boot into a "black screen" recovery and get ADB feedback but that is it.
Strange issue I have here, well it is to me at least, my fathers SGH-I777 the AT&t model boots fine and works when booted but the play store gives me the "no connection" on both wifi and hspa+ and there are a few apps that do not work and cannot be updated for android 4.3 because of the play store. All that is just a day on android and would be fixable if recovery worked. It had or possibly still has clockworkmod recovery installed on it, no idea of the version unfortunately. The first thing that came to my mind was to just update it, well, it cannot be that easy as the latest version of ROM manager does not work, it crashes on startup. So I decided to try ADB and I will get this back if it is in its black screen version of recovery mode
Code:
C:\1>adb devices
List of devices attached
0123456789ABCDEF recovery
C:\1>
and this if it is booted into android
Code:
C:\1>adb devices
List of devices attached
0123456789ABCDEF device
C:\1>
Kind of a side note but also the main issue, when I try to "reboot to recovery" or hold both volume rockers and the power button till to logo appears all I get is a black screen and if it is dark enough in the room you can see that the backlight is on. So I am assuming a corrupted file somewhere, I just need to get somewhere and so far after 3 hours of searching for a solution today I have not. I don't know where to splice this in so i'll do it here; I am pretty sure this is a result of my father having Cyanogenmod updater update from 10.1 to 10.2 without completely re flashing boot and installing from a "factory reset" device then recovering the data.
List of some other things I have tried:
installing the latest apk of the play store
installing the latest apk of ROM manager
not much else that I can think of at this time, but ask and I will either try it or tell you if I have and try again anyways. Not too urgent but thank you for being here xda .
I just read this "http://forum.xda-developers.com/showthread.php?t=1824419" and it looks like rom manager is not a good idea, still need to find a way to install the recovery though and I have no idea how to get fastboot to work without it.
Maybe this post will help...Post #4000 http://forum.xda-developers.com/showpost.php?p=44984062&postcount=4000
Sent from my SAMSUNG-SGH-I747 using xda premium
Put in normal download mode by pulling battery and hold the volume down button as you plug the micro usb in. Reflash to stock jelly bean 4.1.2 using Odin and root with framaroot 1.42 and use aragon exploit and go from there....
Sent from my SGH-I777 using XDA Premium 4 mobile app
Alright ill try that in a few minutes, just left the house.
Starfrog6 said:
I just read this "http://forum.xda-developers.com/showthread.php?t=1824419" and it looks like rom manager is not a good idea, still need to find a way to install the recovery though and I have no idea how to get fastboot to work without it.
Click to expand...
Click to collapse
Just a couple of points, which may be helpful if you are not very familiar with the SGH-I777. Recovery is built into the kernel, not in a separate partition of it's own, so you can't just install a recovery, you must install a kernel containing a recovery.
Rom manager is said to be OK when you have CM on the phone, but in your case it would probably be best to avoid it until the problem is resolved.
The solution 4-2ndtwin posted sounds correct to me. If it were my phone, I'd try that first before flashing back to stock.
4-2ndtwin said:
Maybe this post will help...Post #4000 http://forum.xda-developers.com/showpost.php?p=44984062&postcount=4000
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Sorry for being so late but this worked and allowed me to boot into recovery. Thank you so much!
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.