Related
I have a Milestone which I rooted last week. I am from Romania.
I have overclocked it and it ran smoothly. Yesterday I was playing with the governors modfying files inside the system.
I renamed the mot_boot_mode file under system/bin in mot_boot_mode.bin and added another mot_boot_mode that had these first lines inside it "#!/system/bin/sh
export PATH=/system/bin:$PATH
#run the original binary
mot_boot_mode.bin"
I rebooted and got stuck into the M loop.
What can I do? Please help me!
vladstercr said:
I have a Milestone which I rooted last week. I am from Romania.
I have overclocked it and it ran smoothly. Yesterday I was playing with the governors modfying files inside the system.
I renamed the mot_boot_mode file under system/bin in mot_boot_mode.bin and added another mot_boot_mode that had these first lines inside it "#!/system/bin/sh
export PATH=/system/bin:$PATH
#run the original binary
mot_boot_mode.bin"
I rebooted and got stuck into the M loop.
What can I do? Please help me!
Click to expand...
Click to collapse
If you can't access recovery, then go into fastboot and reflash a sbf.
You likely did not set proper permissions for the new script.
This is not serious trouble, don't worry. If you are rooted I assume you have vulnerable recovery flashed in. Boot in openrecovery and fix the mess over adb or directly from the phone. If you are totally lost, either restore your nandroid backup (you did it right? ). Altternatively reflash the whole SBF as poster above suggested.
i didnt have a vulnerable recovery flashed in...nor a nandroid backup...but i have followed the "back to stock" thread and flashed an original sbf...I set the right permission for the file before rebooting...cant figure out what was wrong... none the less i had a titanium backup done 2 days ago which worked like a charm....
Please advise me guys into doing a nandroid backup and flashing a vulnerable recovery
Sent from my Milestone using XDA App
What advise do you need? There is an in depth instruction on top.
However, it is not very complicated, i can tell since I'm into this about 1 month and succeeded with a minimum or even less amount of knowhow.
The vulnerable recovery is working for all boot loader versions and does allow to access the update.zip.
You'll need either RSD Lite or sb_reflash, depending on your OS. So boot into bootloader mode (holding up the d-pad on start), apply the vulnerable recovery sbf and fire up your update.zip once thee flashing is done. (assuming you have followed the instructions on how to prepare your sdcard for OpenRecovery, eg. the G.O.T distro requires a differnt structure)
If you get a checksumm error, check out the log files and modify the file, or use a script to recalculate the checksum. But this is rarely the case.
Ohh.. and talking about "original sbf", you might want to read the difference between Service and "normal"
MenoDev said:
What advise do you need? There is an in depth instruction on top.
However, it is not very complicated, i can tell since I'm into this about 1 month and succeeded with a minimum or even less amount of knowhow.
The vulnerable recovery is working for all boot loader versions and does allow to access the update.zip.
You'll need either RSD Lite or sb_reflash, depending on your OS. So boot into bootloader mode (holding up the d-pad on start), apply the vulnerable recovery sbf and fire up your update.zip once thee flashing is done. (assuming you have followed the instructions on how to prepare your sdcard for OpenRecovery, eg. the G.O.T distro requires a differnt structure)
If you get a checksumm error, check out the log files and modify the file, or use a script to recalculate the checksum. But this is rarely the case.
Ohh.. and talking about "original sbf", you might want to read the difference between Service and "normal"
Click to expand...
Click to collapse
Whats the difference?
By the way...I didnt had to prepare the sd card in a special way or something...Nor to format it in a particular way...It was pretty easy the whole process though...
Now I have switched to GOT 2.2.1 Froyo with CM6 mod but I'm very dissapointed on the battery life... Think I'm gonna try other 2.2 Roms with 2.1 kernel...
Thanks for your reply!
Know what I observed in my case? Installing the 2.2.1 firmware with no "got-fix" and no root makes my battery last very long
Sent from my Milestone using XDA App
MenoDev said:
Know what I observed in my case? Installing the 2.2.1 firmware with no "got-fix" and no root makes my battery last very long
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
what do you mean by "no got-fix"
Please let me know....And also...Did you have the GOT 2.2.1 where the battery last less?
vladstercr said:
what do you mean by "no got-fix"
Please let me know....And also...Did you have the GOT 2.2.1 where the battery last less?
Click to expand...
Click to collapse
You get the G.O.T 2.01 OpenRecovery Version along with the Firmware files.
Usually one supposed to boot into recovery and apply some mods, the first one would be fix 2.2.1 issues... and so on.
I was lazy and didn't, but simply flashed the Firmware. And to my surprise the battery was lasting longer.
But you know, I can't tell if it's depending on the Distro or whatever. Hovewer, I'm not that of a version junkie, rather looking for a decent distribution, and luckily i found one. Even if it was 2.0 it would have been cool for me. Now 2.3 resp. 3.0 is around the corner, then the whole race starts again...
vladstercr said:
Whats the difference?
By the way...I didnt had to prepare the sd card in a special way or something...Nor to format it in a particular way...It was pretty easy the whole process though...
Now I have switched to GOT 2.2.1 Froyo with CM6 mod but I'm very dissapointed on the battery life... Think I'm gonna try other 2.2 Roms with 2.1 kernel...
Thanks for your reply!
Click to expand...
Click to collapse
Btw... they announced froyo for next week for the milestone in this forum.. so we hopefully will all be fine, if not, we will still have to deal with the fact that Android is very nice, but not yet rock solid
MenoDev said:
You get the G.O.T 2.01 OpenRecovery Version along with the Firmware files.
Usually one supposed to boot into recovery and apply some mods, the first one would be fix 2.2.1 issues... and so on.
I was lazy and didn't, but simply flashed the Firmware. And to my surprise the battery was lasting longer.
But you know, I can't tell if it's depending on the Distro or whatever. Hovewer, I'm not that of a version junkie, rather looking for a decent distribution, and luckily i found one. Even if it was 2.0 it would have been cool for me. Now 2.3 resp. 3.0 is around the corner, then the whole race starts again...
Click to expand...
Click to collapse
Yes... I never applied those fixes too... Still the battery last very little time...
As an example:
Before I went to sleep last night the battery was fully charged...no apps running...3g disabled...everything disabled...phone idle for 7 hours...and when I woke up and check... I got 60% of the battery...
Thats frustrating...
I must admit I have the Cyanogenmod running...Would this be the issue?
Sorry for the long read, this is half rant and half question.
Alright, I got a captivate a long time ago (about a year and 3 months ago), loved it, rooted it and installed cyanogenmod as soon as I got home, changed roms and kernals constantly, did whatever I wanted to do.
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
-Pirate said:
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
Click to expand...
Click to collapse
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
-Pirate said:
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Click to expand...
Click to collapse
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
-Pirate said:
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
Click to expand...
Click to collapse
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
U def don't need a jig. If it's booting it's not bricked. Try removing battery, start Odin, hold down power and down, plug in and put battery in. This should bring u to download mode.
prbassplayer said:
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
Click to expand...
Click to collapse
I did start to see a few people with the problem, however many people do not follow up with what fixes their problem, and I did what a few people had said to do.
prbassplayer said:
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
Click to expand...
Click to collapse
I should of mentioned that I did flash a few times, 3 total I think, it was getting stuck at boot.
prbassplayer said:
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
Click to expand...
Click to collapse
I understand that **** happens but honestly my old captivate could always get into recover mode and download mode no matter what, it's extremely frustrating that something changed with the newer models. One of my questions was what caused the brick? I did nothing wrong from what I see and it was running perfectly until I tried to restart/boot into recovery.
Oh and mbc663, thanks but download mode doesn't work at all, nor does recovery obviously.
I can't say exactly what you are doing. Best advice I can do Re download your .zips Flash back to stock GB and try again.
-Pirate said:
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
Click to expand...
Click to collapse
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Sounds like you got one of the refurbs that is missing the SBL. Have you looked at this thread? http://forum.xda-developers.com/showthread.php?t=1129821
I've not had this problem myself but it sounds like that might help. If I remember reading correctly, once this is flashed it should stick as long as you don't flash any other bootloaders on top of it.
Its not missing the sbl. The sbl it has doesn't respond to key combos. Derpa sherpa moment for samsung I guess?
Rofl yeah...if it was missing the sbl it would be fuggin bricked!
studacris said:
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Click to expand...
Click to collapse
I know, thanks. I'm such a creature of habit, I started doing it like this a bit over a year ago, and has worked flawlessly for me(just jinxed myself!) so I never saw a reason to "fix what aint broke".
I'll take a look at Cezar's thanks!
Yeah, missing SBL was a poor choice of words. My bad.
kangi26 said:
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Click to expand...
Click to collapse
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
kangi26 said:
3buttonFix to my SD, then reboot into recovery
Click to expand...
Click to collapse
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
-Pirate said:
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
Click to expand...
Click to collapse
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
kangi26 said:
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
Click to expand...
Click to collapse
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
-Pirate said:
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
Click to expand...
Click to collapse
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
kangi26 said:
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
Click to expand...
Click to collapse
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: deleted
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
-Pirate said:
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: imgurDOTcom/26sXGl.jpg
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
Click to expand...
Click to collapse
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
kangi26 said:
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
Click to expand...
Click to collapse
Maybe because it's a refurb? and whoops didn't think about that.
-Pirate said:
Maybe because it's a refurb? and whoops didn't think about that.
Click to expand...
Click to collapse
I'm not sure why, mine is a referb, and I have a sticker with mine on it. Ooh well, it is what it is
Sent from a autonomous device
http://www.cyanogenmod.com/blog/cyanogenmod-7-2-0-rc1-is-upon-us
It’s been a long time in the making, but it’s finally here: CyanogenMod 7.2, the latest version based on Android 2.3(.7), has reached the release candidate stage!
We’ve been delaying it for too long, mostly because new devices kept being submitted to us, and now we feel that at 69 70 devices, CM7.2 is more than ready for everybody to enjoy
7.2 adds a couple of backported features and fixes from Android 4 (ICS), over 20 new devices when compared to 7.1, and even some new features to boot (be sure to check out the new predictive contact search in the phone dialer!). We’ve also fixed some bugs along the way. Some of them device-specific, others that affected everybody, and one in particular that’s been plaguing Android for a long time: the mysteriously vanishing SD-card ringtones are no more! You can check the full list of noteworthy changes at the CHANGELOG.
As usual, you can submit bug reports on these builds: if you find anything broken in your device while running CM7.2-RC1, (as downloaded from our mirrors or ROM Manager! Please do not submit reports if your build came from elsewhere), be sure to submit a report through http://code.google.com/p/cyanogenmod/issues/ , so that we can fix it in time for the final 7.2 release.
from Cyanogenmod Blog
What are the significant differences between this official CM7.2 and the unofficial CM7.2 KANG that we have been using in the last couples of months?
Excuse a noob, but is this file good for SD as well as emmc installs?
thanks
Assuming you have already got a flavor of cm7 installed on an SD card you can copy the update file to the boot partition (I did it from my PC with a card reader), then insert the card in your NC and either access your boot menu and select Reboot Recovery or boot normally and then Reboot with the Recovery option. The files unpack and the penguin is displayed. The unit shuts off and you have to restart (seems to take forever with the android boot animation but wait it out) and all should be well.
Sent from my NookColor using Tapatalk 2 Beta-2
votinh said:
What are the significant differences between this official CM7.2 and the unofficial CM7.2 KANG that we have been using in the last couples of months?
Click to expand...
Click to collapse
KANG 03042012, the latest, *has* CM7.2RC1 so the differences are detailed in that thread but boil down to mr666's enhancements.
For instance, I get the impression from your sig that you run Dalingrin's as a separate update. Dalingrin's has been a part of M-K,(one of the above mentioned enhancements), for a while now.
MISRy said:
KANG 03042012, the latest, *has* CM7.2RC1 so the differences are detailed in that thread but boil down to mr666's enhancements.
For instance, I get the impression from your sig that you run Dalingrin's as a separate update. Dalingrin's has been a part of M-K,(one of the above mentioned enhancements), for a while now.
Click to expand...
Click to collapse
Phrrrrrrr??? What???
Forgive me but what are you talking about?
votinh said:
Phrrrrrrr??? What???
Forgive me but what are you talking about?
Click to expand...
Click to collapse
Glad you said it, so I didn't have to show my ignorance
I was happy to see that 7.2 fixed the magazine stacking in the Nook App. I have the official and the M-K running on different NCs and they're running great!
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
Sherip said:
The unit shuts off and you have to restart (seems to take forever with the android boot animation but wait it out)
Click to expand...
Click to collapse
I tried to update but I can't even get to the boot animation. It shows CM is loading, flash of light, then goes black. Time for a fresh install I guess.
bp_ said:
I tried to update but I can't even get to the boot animation. It shows CM is loading, flash of light, then goes black. Time for a fresh install I guess.
Click to expand...
Click to collapse
Took awhile even to get to the animation, you may have given up too soon.
I like the update, have noticed improved battery life, nice colors and screen transitions. I have twice had a glitch where it wouldn't wake up after sleeping (twice in the last few days). Hope that doesn't persist.
Sent from my NookColor using Tapatalk 2 Beta-2
libertus77 said:
I was happy to see that 7.2 fixed the magazine stacking in the Nook App. I have the official and the M-K running on different NCs and they're running great!
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Actually it didn't. It's that Nook for Android released a brand new version that fixed the magazine issue. A week prior the older version still stacked all the magazines on top of each other on my 7.2 build.
How do you know if you have the latest version of the Nook app? Download some comic books, it's the first version that supports Nook Comics.
SeaFractor said:
Actually it didn't. It's that Nook for Android released a brand new version that fixed the magazine issue. A week prior the older version still stacked all the magazines on top of each other on my 7.2 build.
Click to expand...
Click to collapse
Hmm. But is the newer version not stacking on 7.1 either? I'm curious, but not enough to flash back to test, I don't think. I just had a friend switch to 7.2. A few days ago specifically because of the stacking, so that would be a good coincidental timing. Anyone still on 7.1 that can check?
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
libertus77 said:
Hmm. But is the newer version not stacking on 7.1 either? I'm curious, but not enough to flash back to test, I don't think. I just had a friend switch to 7.2. A few days ago specifically because of the stacking, so that would be a good coincidental timing. Anyone still on 7.1 that can check?
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
I had rotated out of 7.1 awhile back and I use B&N app everyday. When they provided the new update for the app, that is when my magazines stacked correctly. The update was actually made for the tablet and the version of the new update is: 3.1.0.19.ANDTBL (and tablet). I updated when it came out and it fixed it immediately. I would think it would still work correctly on 7.1, but like you, do not want to mess with a good think.
Okay, curiosity was bugging me. I tested, and yep, no stacking on 7.1 either, guess it was a B&N fix. 7.2 is good in any case.
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
I did a new install to SD card with the CM7.2RC Most things work as should. Biggest issue is that after some point, the unit will not accept a charge. I plug the cable in (NC Cable/charger) and the light on the cable goes straight to green. Leaving it plugged in for awhile doesn't change the amount of charge (actually is discharging per normal use). After a power off and re-boot, all works as normal. Not sure what the trigger is that causes the Nook Color to not take a charge, but it is not locked up, all programs work normally. It will take a charge and discharge-lets say over a few days, then at some point will not allow a charge. Battery % meter seems to be accurate; tracking appropriately.
I also have a Nightly (#75 I think) SD card that I use, as well as stock Rooted 1.1 on EMMC, and neither have this issue, device is fine electronically.
Any ideas?
Thanks, Mark
Are you sure it's not the cable? They have a bad habit of going south on us.
CM7.0.3 to CM7.2 non rooted on SD card
Hello,
I'm a noob here and found that I should ask questions here on the general forum and not the developers forum.
I have very recently created a sd card non rooted using CM7.0.3 encore and have kernel version 2.6.29-omap1 and its Android version 2.3.3.
I want to keep the ability to return to B&N mode from internal memory to keep my warranty from B&N in check.
I have had issues with using the Google Market app and don't see a lot of apps that I would normally see on my Droid Bionic...like Facebook and others. I have hacked around that issue by finding apps and manually installing them as a work around which is fine for now.
A couple of questions?
By going to a nightly version...can I still remain non-rooted and keep emmc stock and intact with B&N Color flash and boot from my sd card?
will this fix my Google Market issues and have more applications that I can see?
Will I be able to just drag the new CM7.2 ??version code to my /boot directory on my sd card and go into recovery mode to boot it in?
Does this new CM7.2 ??? get put in a particular partition or just under the /boot directory?
Will this wipe out my apps or any data on my sd card?
Will this CM7.2 ??? version support USB host mode for a USB webcam for Skype?
Apparently, this opens another can of worms in that I need to provide USB power from an external hub and I need some kind of Nook Tweaks app to adjust settings?
Can someone explain this?
I have searched these forums and I must say spent a lot of time and nothing seems to be in one place or current on pre-requisites.
Should I get a second sd card to practice on so I don't wipe out my bootable CM7.0.3 version
Any help here would be GREAT!
Thanks in advance!
BB
I'm in a similarsituation as BeaconBob. The following applies to me as well.
BeaconBob said:
... using CM7.0.3 encore and have kernel version 2.6.29-omap1 and its Android version 2.3.3.
A couple of questions?
Will I be able to just drag the new CM7.2 ??version code to my /boot directory on my sd card and go into recovery mode to boot it in?
Does this new CM7.2 ??? get put in a particular partition or just under the /boot directory?
Will this wipe out my apps or any data on my sd card?
Should I get a second sd card to practice on so I don't wipe out my bootable CM7.0.3 version
Any help here would be GREAT!
BB
Click to expand...
Click to collapse
I set up my 8GB card months ago and have forgotten all the details of flashing a ROM. Thanks for any suggestons/help.
Make sure your screen density is set to 180. Clear market cache and data, reboot, and try again.
If you don't want to spring for a new Sandisk class 4 card -- I have five now ) -- just use your Win32Disk Imager to write an image file of your current setup to your computer and go blithely on experimenting like crazy. You will always have an image file to write back to your freshly formatted sd card to take a giant leap backward. But I'd bet you'll never even use it. It's too much fun going forward.
And it never hurts to have a zipped backup of the Titanium BU files available to upload and restore at various stages.
Currently running a racks triple boot, the latest Kang cm7, a dualboot miui/stock, and somewhere I could swear I had an old 253m from back in january. Just so my NC flap doesn't break, I'm good...
Okay, looking to get more involved and learn a lot more in hopes of contributing someday but for now I'm stuck. I picked up a very used Droid 3 on Ebay and rooted it with MotoFail, then installed SafeStrap 3.05 & everything seemed fine. Problem is I can't boot into any "safe" ROM slots, it just gives me a blank black screen & I have to remove the battery to restart. My original D3 has CWM on it, but I was always too scared to flash anything too drastic so this is my test toy. It is running on the 906 with SS version 3.05.
I downloaded a bunch of ROMs and none work. I tried restoring my backup which I'm sure I saw somebody do on Youtube but I have since read that won't work anyway but I'd still like a "stock" rom in a safe slot. I also tried the official 906 zip, but also read somewhere that that only works on the stock partition. I tried aokp_toroplus_nightly_2013-08-20.zip, D3-Eclipse-v3.0_NON.zip, minimoto_v1.7.zip, & the afore mentioned VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.XML.zip but none would even flash, just gave errors. Also tried KEXEC-cm-9-20120905-UNOFFICIAL-solana-SS2.zip, Liquid-JB-v2.9-OFFICIAL-solana.zip, & something small called phablet-20130327-cm_solana.zip. That last one, tried usually in slot 4, is the only one that does something other than give a black blank screen - it eventually shuts the phone off. I read that Liquid had to be in slot 3 so that's where I put it every time.
I DID discover that I don't think Busybox was installed during the root this time, when I rooted my original D3 it was already there. So I installed a BB from Market, then went into SS & uninstalled, then reinstalled. Rebooted into recovery and re-wiped all the slots (except stock of course) with all 4 options (cache, dalvik, system, & uh, something else I forget now) & re-installed the ROMs but nothing changed.
More possible helpful info: When this BB installed it gave me an option of normal install or more thorough "smart" install, I did the smart install, also installed CWM ROM Manager to try something but that didn't work either, and downloading official ROMs through that always gives an error. Data sizes of slots are all 2GB except #4 which is only 1GB. Under the "Mount" tab, system & (either data or cache, can't remember) are unchecked, and the 3 "unmount" boxes below are checked. Using a root explorer, I can confirm that SS did "install" the roms & each slot contains a cache.img, system.img, & a userdata.img.
So, what am I doing wrong guys? Any help or ideas would be greatly appreciated! Sorry for being such a noob here, Thanks in advance!
I think I would just start over. FXZ the phone back to stock and re-root with Motofail. Make sure that you unzip the Motofail download and disable any virus checker you have. It does sound possible that the lack of busybox may be the cause of your flash failures. I can tell you for 100%, absolute, certain that Minimoto will flash on any ROM slot in Safestrap 3.0.5.
Eclipse 3.0 as you download will not install in Safestrap, but I created a Safestrap-enabled version. You can find it here: http://www.droidforums.net/forum/teamhaters/210971-eclipse-v3-0-droid-3-port-11.html#post2414744
I think that the Dropbox link is still live. Let me know if it's not there...
All of the KEXEC ROMs, if I am not mistaken, have to be installed in ROM Slot 1. (I never used them, beyond just seeing what it looked like, and it's been a while since I tried.)
Get Motofail here: http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
It says it's for the D4, but it's what the D3 will be rooted with as well.
Success!!! Thank you!!! I am now up & running with all 4 slots filled, currently with Avatar, Maverick, Dark Droid, and a generic non-VZW stock. The Eclipse links were down (Dev Host) but if you still have an Eclipse for SS I would love to take a look at it. Already tried the Ubuntu Touch one too, "Phablet" or something, but couldn't get at a menu to connect to my WiFi. And, since you are so helpful... I was wondering if you could point me to some stuff to read & research. There are plenty of guys (& a few girls I'm sure too) making great ROMs but they need to be ported to different devices. So I would like to eventually learn how to port SS to different devices and ROMs to SS. It seems there are really only a few people working on that stuff and that is where the help would be needed. Working my way through the XDA University thing too. Thanks again for your help!
I'm glad you got that figured out.
Lobstercat said:
The Eclipse links were down (Dev Host) but if you still have an Eclipse for SS I would love to take a look at it.
Click to expand...
Click to collapse
The Eclipse that you were trying to download isn't Safestrap ready anyway, but I created one that's on my Dropbox: https://www.dropbox.com/s/hyl3gzurgh8bvdw/Eclipse3.0-SS3-signed.zip
doogald said:
I'm glad you got that figured out.
The Eclipse that you were trying to download isn't Safestrap ready anyway, but I created one that's on my Dropbox: https://www.dropbox.com/s/hyl3gzurgh8bvdw/Eclipse3.0-SS3-signed.zip
Click to expand...
Click to collapse
uploaded copy to http://d-h.st/xFd
So ive been trying to dual boot because i want to try aosp based rom but i need to be a ble to get back to touchwis. Now ive tried the patcher app which aome people said it worked but ive tried everything with no succes.
egren58 said:
So ive been trying to dual boot because i want to try aosp based rom but i need to be a ble to get back to touchwis. Now ive tried the patcher app which aome people said it worked but ive tried everything with no succes.
Click to expand...
Click to collapse
I dont't know if this helps but in the thread for the patcher app it was mentioned that if you needed to dual boot with a TW based rom it would need to be the primary in order for it to work properly otherwise the mods would need to be patched before flashing.
glm0025 said:
I dont't know if this helps but in the thread for the patcher app it was mentioned that if you needed to dual boot with a TW based rom it would need to be the primary in order for it to work properly otherwise the mods would need to be patched before flashing.
Click to expand...
Click to collapse
I swt tw as primary patched cm12 and gapps. But recovery was freezing so i tried to manually paych the file as stated. But than when i got to flash vie recovery it says fail. I have no idea what to do since i did exactly as it said.
My guess would be try asking in the dual boot thread. Others have gotten it to work.
BAD ASS NOTE 4
BACARDILIMON said:
My guess would be try asking in the dual boot thread. Others have gotten it to work.
BAD ASS NOTE 4
Click to expand...
Click to collapse
Good idea. But for some reason i cant find the dam thread now. Wtf.
egren58 said:
Good idea. But for some reason i cant find the dam thread now. Wtf.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3058835
All u need
BAD ASS NOTE 4
http://www.linuxmolecule.com/how-to-dual-boot-roms-on-the-galaxy-note-4/
I can confirm this works in T-Mobile note 4. You just have to follow the steps.
It works trust me, I'm a senior member
I managed to get it to flash but....
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Dhat Boi Swerve said:
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Click to expand...
Click to collapse
It should when you reboot the device.
Dhat Boi Swerve said:
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Click to expand...
Click to collapse
Struggling with this thing for the last 2 days. Same issue as your. Cannot switch back to the primary rom...
suhridkhan said:
Struggling with this thing for the last 2 days. Same issue as your. Cannot switch back to the primary rom...
Click to expand...
Click to collapse
you cant dual boot stock Samsung roms for some reason...
frr1 said:
you cant dual boot stock Samsung roms for some reason...
Click to expand...
Click to collapse
Just got it working, after so much trouble. Tmobile Note4 running TW Rapture as primary and CMRemix as secondary. Still no luck with the second step of patching, but manual patch has worked. This one is a better written guide, I suppose.
http://www.linuxmolecule.com/how-to-dual-boot-roms-on-the-galaxy-note-4/
I can't believe it's taken me this long to get into trying to dual boot my phone... both my desktop and laptop have ridiculous multi-boot schemes :laugh:
The main reason I haven't yet delved into this is a fairly simple question that I haven't been able to find the answer to: How much free storage space is required / will be used by installing an additional ROM and on which partition(s)?
I'd really appreciate if anyone who has this working could fill me in on that info
BTW another great thread with instructions, etc. is here: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
jazzmachine said:
I can't believe it's taken me this long to get into trying to dual boot my phone... both my desktop and laptop have ridiculous multi-boot schemes :laugh:
The main reason I haven't yet delved into this is a fairly simple question that I haven't been able to find the answer to: How much free storage space is required / will be used by installing an additional ROM and on which partition(s)?
I'd really appreciate if anyone who has this working could fill me in on that info
BTW another great thread with instructions, etc. is here: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
Click to expand...
Click to collapse
AOSP roms has very small footprint, that's why they are insanely fast... The roms itself with gapps only takes about a gigabyte, if it's CM or other aosp roms. If you dual boot 2 TW roms, of course it's gonna take huge space. It also depends on how many apps you are going to install on the second rom