Related
To start, the other day I installed cm9 .04 with cyanoboot w/ twrp. Everythings been fine. Running cm9 mostly until I need something it can't do, then flash cm7 backup. Last night I was using twrp to compress the backups of each. During one of the times (I don't remember which rom I was running) after everything was compressed, wiped, and restored, I began getting the cyanoboot boot loop where when it restarts it goes to the cyanoboot screen and before you can press the n, it runs revovery. I noticed it runs to E9 and the next time shows E0. I tried the dd thing I saw at the end of the cyanoboot thread while in recovery from a booted cwm sdcard. I did it twice. Adb showed it running the process. At the end, I wasn't sure what to do, so once I tried reboot recovery and the next time I tried reboot. Each time it goes to cyanoboot starting recovery.
Any ideas on what to do? Should I flash cwm recovery? If so, then my saved backups are useless. Is there another way to force cyanoboot to run the rom installed on emmc instead of going to recovery?
Thanks ahead of time for any insight.
Sent from my PG06100 using xda premium
there is this utility app on the play store called :
4EXT Recovery Control
https://play.google.com/store/apps/...GwsMSwxLDEwOSwiZXh0LnJlY292ZXJ5LmNvbnRyb2wiXQ..
.
and honestly, i am too stupid to understand if it would or would not be of any help.
old_fart said:
there is this utility app on the play store called :
4EXT Recovery Control
https://play.google.com/store/apps/...GwsMSwxLDEwOSwiZXh0LnJlY292ZXJ5LmNvbnRyb2wiXQ..
.
and honestly, i am too stupid to understand if it would or would not be of any help.
Click to expand...
Click to collapse
Please stop posting entirely unhelpful information. If he can't boot into internal emmc how do you expect him to use this app, even if it is something that could be helpful?
---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------
@ OP:
Your device is going straight to internal recovery? Perhaps try restoring your backup again? Or flash cm9 fresh?
Also, what do you mean by "compressing" recoveries? I haven't really working with TWRP before, so not sure if this is something unique to it or if you're just using a different term for something I am familiar. with.
I tried several different versions of the backups, both compressed and uncompressed. Tried fresh installs of cm7 and 9. Still nogo. I've been looking at adams ubuntu unbrick. I may try that. I was hoping there might be a quick fix.
Oh. And yes, its boot looping to internal twrp recovery. I can get a cwm recovery sdcard to boot.
Twrp gives you several options in your backups. You can select what parts you want backed up (system, data,etc), md5 or not, and compressed or uncompressed. Compressed takes longer but the size is hella smaller.
I prefer twrp for several reasons: touch ui, more options, file manager and more. But, as stated in the dev thread, its got bugs. Call me hell bent for disaster, but even if I have to flash another recovery or even start fresh from unrooted stock, I'll go back to cyanoboot and twrp.
Sent from my PG06100 using xda premium
ok. i downloaded adamoutlers ubuntu recovery. i ran it by the instructions. when it tried to boot, i got a black screen with some squiggly lines on the volume button side of the screen and then it did the normal bootloop process. before this, i was able to use a boot sdcard and install cwm to emmc. it doesn't have cyanoboot coming up anymore. but i still get the bootloops to recovery. i don't know if the adamoutler download was corrupted. i haven't been able to find an md5 sum for it. i've downloaded it again, and plan on downloading it a third time. i'll then compare the md5 sums of all 3.
i'm beginning to worry that i may have a damaged internal storage.
i also tried albertwertz recovery rom before the ubuntu recovery.
if anyone has more input, i would be grateful.
EDIT:
i ran md5 check sum on all three downloads. all were the same: 97befcb53ee04306c59d24b0ddd26ceb
i presume that's right, or i got three identically screwed up downloads.
if someone would check that i would appreciate it.
i'm about to try aspipatel's windows 7 method. i used it to unroot before.
I looked around for anyone else that may have experienced this however I couldn't find anything close. I flashed the P7510 UK ROM after a Nandroid and noticed it formatted my entire tab so I lost everything including my Nandroid backups. (I flash a lot and copy off to PC sometimes so I was only pissed that I lost some of my GTA III game progress) but did anyone else have that happen? Usually when I flash ROMs either via CWM or Odin it doesn't blow away my entire storage. The only goof I had was when I used Mobile Odin to flash initially I forgot to wipe data and cache therefore I went into stock recovery (after being stuck on the Samsung screen for a bit) and did the wipe.
Just curious if anyone else had this or if my mistake could have been the cause.
jrodd77 said:
I looked around for anyone else that may have experienced this however I couldn't find anything close. I flashed the P7510 UK ROM after a Nandroid and noticed it formatted my entire tab so I lost everything including my Nandroid backups. (I flash a lot and copy off to PC sometimes so I was only pissed that I lost some of my GTA III game progress) but did anyone else have that happen? Usually when I flash ROMs either via CWM or Odin it doesn't blow away my entire storage. The only goof I had was when I used Mobile Odin to flash initially I forgot to wipe data and cache therefore I went into stock recovery (after being stuck on the Samsung screen for a bit) and did the wipe.
Just curious if anyone else had this or if my mistake could have been the cause.
Click to expand...
Click to collapse
I too experienced the same problem. I think this happened because i performed the wipe operation using the stock recovery.
jrodd77 said:
I looked around for anyone else that may have experienced this however I couldn't find anything close. I flashed the P7510 UK ROM after a Nandroid and noticed it formatted my entire tab so I lost everything including my Nandroid backups. (I flash a lot and copy off to PC sometimes so I was only pissed that I lost some of my GTA III game progress) but did anyone else have that happen? Usually when I flash ROMs either via CWM or Odin it doesn't blow away my entire storage. The only goof I had was when I used Mobile Odin to flash initially I forgot to wipe data and cache therefore I went into stock recovery (after being stuck on the Samsung screen for a bit) and did the wipe.
Just curious if anyone else had this or if my mistake could have been the cause.
Click to expand...
Click to collapse
Wich CWM recovery u used.?
Vinchenzo13 said:
Wich CWM recovery u used.?
Click to expand...
Click to collapse
I didn't have CWM installed yet, just used stock recovery wipe. Sounds like another experienced the same thing so I may just consider it to be caused by stock recovery wipe.
jrodd77 said:
I didn't have CWM installed yet, just used stock recovery wipe. Sounds like another experienced the same thing so I may just consider it to be caused by stock recovery wipe.
Click to expand...
Click to collapse
Stock recovery,where u get one,so it happens i just need to format everything,maybe then my storage will be fixed lol
Vinchenzo13 said:
Stock recovery,where u get one,so it happens i just need to format everything,maybe then my storage will be fixed lol
Click to expand...
Click to collapse
Ahh, i didn't realize you were OP from the other thread regarding storage. Not sure if that will work, it may just reformat your 2GB but hell maybe worth a shot.
Starting from a power off I just hold Vol - and Power button until i get to the Recovery/Download icons, hit Vol - to highlight the left icon (recovery) and Vol + to select it. it looks kinda like CWM and it allows you to reformat. maybe you can fix the partitions in there.
Hey folks,
So the end of Q3 came with no ICS so I decided it was time to learn about modding these phones. I have modded Xboxes etc so I figured I would try to take this on.
My Phone:
AT&T MB860 bone stock with 4591 on it when I started.
I was able to unlock the phone following a tutorial on youtube. Then I tried to reflash CWM and CM7 using AUTOMATIC_UNLOCK_V4.2. Thats where things went wrong. The phone got stuck at the Dual core screen (to be honest I might not have waited 10 minutes after flashing).
So now here I am the battery is drained so I am using a cut off USB cable for power. When the phone is booting it says "unlocked" in the top left corner I can access all of the menus. When I choose recovery the phone boots into ClockWork Mod recovery. I am hoping I am half way there and the kind folks here can guide me to the finish. If not I'm open to starting from scratch whichever is going to be fastest. I'll attach a few pics for reference
Mycotopian said:
Hey folks,
So the end of Q3 came with no ICS so I decided it was time to learn about modding these phones. I have modded Xboxes etc so I figured I would try to take this on.
My Phone:
AT&T MB860 bone stock with 4591 on it when I started.
I was able to unlock the phone following a tutorial on youtube. Then I tried to reflash CWM and CM7 using AUTOMATIC_UNLOCK_V4.2. Thats where things went wrong. The phone got stuck at the Dual core screen (to be honest I might not have waited 10 minutes after flashing).
So now here I am the battery is drained so I am using a cut off USB cable for power. When the phone is booting it says "unlocked" in the top left corner I can access all of the menus. When I choose recovery the phone boots into ClockWork Mod recovery. I am hoping I am half way there and the kind folks here can guide me to the finish. If not I'm open to starting from scratch whichever is going to be fastest. I'll attach a few pics for reference
Click to expand...
Click to collapse
(I went through this today, I needed to use option 6 in automatic unlock 4.2 before I could get a Rom on my phone.) this was wrong, tried so many things I got confused, go to this thread:
[Unlocked Only][RECOVERY][2011-11-14] Custom CWM-based Recovery 5.0.2.7-atrix5 in ATRIX android development
and download one of the zipped recoveries, flash through recovery to get a modified CWM that left me install a Rom. I was stuck at the same screen as you before I did this now I'm up and running with MROM.
Your recovery is too old. Get a newer version of CWM. Try flashing this. If you can't you will have to fastboot flash a newer recovery.
Flash ROMs with CWM, not automated tools. CWM is the safest way. As soon as you get a new recovery installed create a backup. Good luck!
okay guys I'm jammed up I download the file CWM_Atrix4G_5.0.2.0 and copied it to a clean microsd. Then I went through the recovery menu
Install zip from sdcard>choose zip from sdcard>
In the next folder list I am unable to find the CWM file. Any tips on how to get the file straight onto the phones internal flash? Maybe through RSD?
Dude, you're trying to install recovery from the recovery... Doesn't really make sense, does it?
Use fastboot instead.
Avoid RSD at all costs.
ravilov said:
Dude, you're trying to install recovery from the recovery... Doesn't really make sense, does it?
Use fastboot instead.
Avoid RSD at all costs.
Click to expand...
Click to collapse
You can't do a first install of recovery from recovery. But you can update (assuming recovery is functioning - even partially).
upndwn4par said:
You can't do a first install of recovery from recovery. But you can update (assuming recovery is functioning - even partially).
Click to expand...
Click to collapse
Yeah, I know. You posted a flashable ZIP, the only one I am aware of.
I'd still recommend a standard fastboot flash though.
ravilov said:
Yeah, I know. You posted a flashable ZIP, the only one I am aware of.
I'd still recommend a standard fastboot flash though.
Click to expand...
Click to collapse
Huh? The only one? Did you search?
upndwn4par said:
Huh? The only one? Did you search?
Click to expand...
Click to collapse
No... Not really.
Hey, I said "that I'm aware of".
ravilov said:
No... Not really.
Hey, I said "that I'm aware of".
Click to expand...
Click to collapse
I have flashed recovery with fastboot exactly once - when I unlocked by bootloader. Ever since it has been flashable zips.
Okay I successfully flashed the new recovery to v5.0.2. Then I chose "apply /sdcard/update.zip" I received the "Install from sdcard complete message" I then chose "+Go Back+" then "reboot". The phone rebooted and sat at the logo with "unlocked" in the corner for a few minutes. I thought maybe I needed to clear it by pulling the battery for a few seconds, which I did. then I let it sit on my desk for 20 minutes at the logo screen.
do need to go in and clear cache? is there another file I should try to flash?
Any input would be appreciated.
Mycotopian said:
Okay I successfully flashed the new recovery to v5.0.2. Then I chose "apply /sdcard/update.zip" I received the "Install from sdcard complete message" I then chose "+Go Back+" then "reboot". The phone rebooted and sat at the logo with "unlocked" in the corner for a few minutes. I thought maybe I needed to clear it by pulling the battery for a few seconds, which I did. then I let it sit on my desk for 20 minutes at the logo screen.
do need to go in and clear cache? is there another file I should try to flash?
Any input would be appreciated.
Click to expand...
Click to collapse
You probably need to re-flash your ROM.
Wipe data, cache, Dalvik, then flash ROM.
upndwn4par said:
You probably need to re-flash your ROM.
Wipe data, cache, Dalvik, then flash ROM.
Click to expand...
Click to collapse
I ran the wipe, cache, davlik then reran the update.zip.
I am still stuck at dual core screen with unlocked the corner.
Mycotopian said:
I ran the wipe, cache, davlik then reran the update.zip.
I am still stuck at dual core screen with unlocked the corner.
Click to expand...
Click to collapse
Umm... That would just install the recovery again. You need to flash a ROM. Seems like your boot partition (aka. the kernel) is borked.
ravilov said:
Umm... That would just install the recovery again. You need to flash a ROM. Seems like your boot partition (aka. the kernel) is borked.
Click to expand...
Click to collapse
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Mycotopian said:
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Click to expand...
Click to collapse
I just installed CM7 on my Atrix last week. Don't forget to install gapps like I did. I had to install them as a zip from the recovery, but I think it's also possible to use the ROM Manager app.
Look for the Google Apps section on this thread: forum.xda-developers.com/showthread.php?t=1257574 This will have the Market (now Google Play) so you can download more apps.
After that, play with all the features! I started with Menu > Settings > CyanogenMod Settings and started playing around. Don't play with the performance settings without knowing what they do.
Also, Make a backup! Make a backup! Make a backup! It may save you when little else will.
Sent from my MB860 using xda app-developers app
Mycotopian said:
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Click to expand...
Click to collapse
Awesome! Enjoy!
Hello,
Please save me from a child who saw me working on her potentially new tablet and possibly broke it
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2037368
Very well written, and all was going well up until the very last step which was to use TWRP to flash sgt7-10-20121124-UNOFFICIAL-acclaim.zip and gapps-jb-20121011-signed.zip which I assume was a JB upgrade from CW7. TWRP started with the SGT7 file, and simply sat there for 30 minutes on install. It would not move, figured I was stuck - so I hard-powered the device off, booted with the CWM recovery SD card I made using this process (BTW the CW7 and 10 roms and Gapps were on a 2nd SD card), so booted into CWM recovery card, tried to flash SGT7 file that way since it worked so well on the cm-7-TEAM-B-BETA1-signed.zip file from earlier - it says it succeeded, however the gapps failed (indicating BAD - dunno why) but figured I could at least boot the device - I was very wrong.
The state I'm in now - endless boot loop. I get the "hold N for menu" boot screen (guess that's cyanoboot), but it will cut off after about 10 seconds and start again. If I hold N, I have 3 lit options (out of about 7 - the other 4 having to do with EMMC are ghosted) - EMMC normal, EMMC recovery, and start fastboot.
After this mess, as it turns out, I do still have recovery (TWRP 2.1.4 I think is the version) - I tried using it to reinstall the cm-7-TEAM-B-BETA1-signed.zip along with its gapps, but despite a success message, the endless boot problem continues. I tried basically starting over with the guide to reinstall cm-7-TEAM-B-BETA1-signed.zip, but same result, successful install of the zip, but still endless boot loop.
I have 2 questions please:
I have a friend with the exact same device (16gb) - and he has TWRP as well - if I asked him to make a full backup of everything of his, could I then use mine to restore it to my device and possibly get a working unit?
If the answer to the first is NO, can someone point me to a potential means to get out of this so I don't have to wear the dumbass medal of shame in front of my daughter? LOL. Thanks in advance.
funnel71 said:
Hello,
Please save me from a child who saw me working on her potentially new tablet and possibly broke it
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2037368
Very well written, and all was going well up until the very last step which was to use TWRP to flash sgt7-10-20121124-UNOFFICIAL-acclaim.zip and gapps-jb-20121011-signed.zip which I assume was a JB upgrade from CW7. TWRP started with the SGT7 file, and simply sat there for 30 minutes on install. It would not move, figured I was stuck - so I hard-powered the device off, booted with the CWM recovery SD card I made using this process (BTW the CW7 and 10 roms and Gapps were on a 2nd SD card), so booted into CWM recovery card, tried to flash SGT7 file that way since it worked so well on the cm-7-TEAM-B-BETA1-signed.zip file from earlier - it says it succeeded, however the gapps failed (indicating BAD - dunno why) but figured I could at least boot the device - I was very wrong.
The state I'm in now - endless boot loop. I get the "hold N for menu" boot screen (guess that's cyanoboot), but it will cut off after about 10 seconds and start again. If I hold N, I have 3 lit options (out of about 7 - the other 4 having to do with EMMC are ghosted) - EMMC normal, EMMC recovery, and start fastboot.
After this mess, as it turns out, I do still have recovery (TWRP 2.1.4 I think is the version) - I tried using it to reinstall the cm-7-TEAM-B-BETA1-signed.zip along with its gapps, but despite a success message, the endless boot problem continues. I tried basically starting over with the guide to reinstall cm-7-TEAM-B-BETA1-signed.zip, but same result, successful install of the zip, but still endless boot loop.
I have 2 questions please:
I have a friend with the exact same device (16gb) - and he has TWRP as well - if I asked him to make a full backup of everything of his, could I then use mine to restore it to my device and possibly get a working unit?
If the answer to the first is NO, can someone point me to a potential means to get out of this so I don't have to wear the dumbass medal of shame in front of my daughter? LOL. Thanks in advance.
Click to expand...
Click to collapse
I don't know if restoring from backup will help, lets keep that option for later.
If you are able to enter twrp, I suggest you flash a cwm 6 flashable .zip, I think the older twrp had some bugs. I use cwm6.012. Now enter that, and flash only the cm10 Rom, don't worry about gapps now. Then factory reset and reboot device.
Let me know what happens then.
I don't believe it's bricked, its probably a cyanoboot issue. What happens if you hold the n button, then select first option? It looks like device is not finding the Rom, hence rebooting.
Sent from my ST27i
When you say flash a CWM 6 flashable zip I assume you mean CWM recovery, to which I do have recovery on an SD card as well as TWRP internal, and I do believe I did try flashing the 10 back in as you indicated, and even tried flashing the 7 back in as you indicated - it showed success, but left me in the same boot loop. I can certainly try again - unsure what the actual version is on the SD card because I'm not at home to check it, so I'm at the disadvantage, but thank you for reading this and trying to help, very much appreciated - will try again and get back to you.
funnel71 said:
When you say flash a CWM 6 flashable zip I assume you mean CWM recovery, to which I do have recovery on an SD card as well as TWRP internal, and I do believe I did try flashing the 10 back in as you indicated, and even tried flashing the 7 back in as you indicated - it showed success, but left me in the same boot loop. I can certainly try again - unsure what the actual version is on the SD card because I'm not at home to check it, so I'm at the disadvantage, but thank you for reading this and trying to help, very much appreciated - will try again and get back to you.
Click to expand...
Click to collapse
Also, in recovery, go into mounts and storage, mount system partition, then try flashing the Rom.
Do not format anything in mounts and storage.
Sent from my ST27i
OOOO...that's one thing I did NOT try... When I was in recovery, system and sd card were unmounted by default...I mounted the SD card so it would find the ROM zips, but did not mount system, thinking "it will do that on its own when it's ready"...wonder if that was unmounted, why I'd get a success message off of trying to flash the GB zip...oh well, good suggestion, will try asap, ty
funnel71 said:
OOOO...that's one thing I did NOT try... When I was in recovery, system and sd card were unmounted by default...I mounted the SD card so it would find the ROM zips, but did not mount system, thinking "it will do that on its own when it's ready"...wonder if that was unmounted, why I'd get a success message off of trying to flash the GB zip...oh well, good suggestion, will try asap, ty
Click to expand...
Click to collapse
It should mount system by default, but no harm mounting it manually.
Do not mount sdcard, unless it doesn't show the zip files.
Sent from my ST27i
That is why I mounted SD, because it didn't have it mounted, and I could not see anything, especially the zips...OK will try this later today, TYVM.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
FWIW I had huge problems when trying to use TWRP. It didn't see my sd-card as it should, and I have heard others having similar issues. I didn't try too much, but went on with CWM instead, following the steps I posted here:
http://forum.xda-developers.com/showthread.php?t=2081981
(At one point while struggling with TWRP I messed up bad enough to get into a boot loop. I solved it ny running the repart.img that is mentioned here and there)
I'm sorry, what is that repart img? Is that the "unbrick your nook using ubuntu" thing I saw in dev but can't download? Do you happen to have it somewhere? LOL
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
No, it's not the Ubuntu thing. It's the one in this article:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Just wanted to throw this out here from the original post on this thread too.
Dang, But all's not lost, If you can get into TWRP like you say do a full wilpe of everything and try to reflash CM7, If that doesn't get you going I would recommend starting over to insure all is well. It's actually hard to really "brick" a NT and there are many good threads here but I have used this one and it's pretty simple to get you back to factory 1.4.3 http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Lets go from there, I'll be around to help except between 3:30 - 5:30 CST, But will do what ever I can to get ya up & runnin.
Thank you kind sir. I've been given a number of ideas, so will be sure to try them. I assume when you say full wipe of everything, you're referring to system, data, and all caches?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
funnel71 said:
Thank you kind sir. I've been given a number of ideas, so will be sure to try them. I assume when you say full wipe of everything, you're referring to system, data, and all caches?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Not exactly sure what goin on in there but if you can get to a recovery menu then it's possible to just fact/dalv/cache wipe ect to clean the garbage and try a fresh install. (maybe) but the back up plan is sure to work if that doesn't
funnel71 said:
Thank you kind sir. I've been given a number of ideas, so will be sure to try them. I assume when you say full wipe of everything, you're referring to system, data, and all caches?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
No do not wipe anything in mounts and backup. Formatting the bootdata, factory partition and some of the other partitions WILL brick your device. Only cache partition can be wiped (do factory reset)
Sent from my ST27i
funnel71 said:
...
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2037368
Very well written, and all was going well up until the very last step which was to use TWRP to flash sgt7-10-20121124-UNOFFICIAL-acclaim.zip and gapps-jb-20121011-signed.zip ...
The state I'm in now - endless boot loop. I get the "hold N for menu" boot screen (guess that's cyanoboot), but it will cut off after about 10 seconds and start again. If I hold N, I have 3 lit options (out of about 7 - the other 4 having to do with EMMC are ghosted) - EMMC normal, EMMC recovery, and start fastboot.
...
Click to expand...
Click to collapse
You can either:
Try flashing CM10 again, using a much less circuitous process such as the one described at http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1; or,
Try restoring to stock using the info/tools from https://github.com/succulent/acclaim_recovery_sdcard.
And in case you're tempted to use any of the so-called "unbrick" tools/methods, first read http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31
SUCCESS!!
OK, equipped with 2 SD cards, 2gb for boot into CWM v6012 recovery and 16GB with JB ROM, GAPPS, and updated CWM 6027 recovery for EMMC...
Attempt #1
Booted into CWM SD recovery via PC usb
Swapped SDs to the 16 with the roms and new cwm emmc recovery
Flashed CWM emmc recovery - success (so now twrp that I had should be gone)
Reboot into system and held N to get to cyanoboot menu & selected internal emmc recovery - success, now in CWM 6027 emmc recovery
Selected install zip from sd card (16 still inserted), flashed sgt7-10.1-20130131-0219-acclaim-meghd00t.zip - success
Selected install zip - flashed gapps-sgt7-10.1-20130131-0219-acclaim-meghd00t.zip (I renamed it to match the other, but it's what came with it in the dev post I got it from) - success
Selected to wipe cache, then went to advanced and wiped dalvik cache - success on both.
Hmm, no main menu, it indicates it wiped it, but stayed still at that point, held power button to power off, turned back on, held N to get back into cyanoboot menu just to view its appearance, seemed normal, selected internal EMMC normal..black screen for several seconds, cyanogen loopy design spins (getting a tad happier), will just let this spin for a while... sure beats seeing a bootloop...
5 Minutes later, still getting the loopy design spin, assuming it's unable to boot, did a hard poweroff, removed SD, started again, this time just letting it run, got the cyanogen spin thing again... assuming it will not boot after 5 minutes.
Attempt #2
Repeated the same process as 1, only this time flashed TWRP recovery 2.2.2.0 into EMMC
Using TWRP, flashed the same jb rom and gapps - reboot
Exact same result.
Attempt #3
Decided to change SD cards the ROM and gapps is being loaded from, because I've heard to use a class 4 card, and the 16GB is a class 10 - changed to an old class4 512MB card - repeated the above process - whoa, twrp is gone, but I didn't flash emmc recovery...is that in the ROM perhaps?? Oh well, tried to flash with this older SD card - Ooo, getting farther, the loopy thing changed shape and now is in the center of the screen (slightly excited) - I may have it!!
Going through set up now!! Going to call this portion a success. Other problems should probably be a new thread as this was resolved...
Ultimate cause - too good of an SD card???? Seriously? Oh well, got er done. thanks to all of you for the ideas. They truly helped.
Just noticed something in your description. You should do the wiping before you flash the ROM not after.
Sent from my NookTablet using Tapatalk 2
asawi said:
Just noticed something in your description. You should do the wiping before you flash the ROM not after.
Sent from my NookTablet using Tapatalk 2
Click to expand...
Click to collapse
Point well taken, thanks much. I was backwards
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
asawi said:
Just noticed something in your description. You should do the wiping before you flash the ROM not after.
...
Click to expand...
Click to collapse
Actually, data/cache/dalvik cache just need to be wiped before first boot of the new ROM.
Of course the order doesn't matter! I really must stop reading the forum (or at least stop writing!) in the middel of the night! (I'm in Sweden). My brain moves slow enough even at it's best... Sorry!
So I was messing around with resolution and DPI settings. Changed it to 1920x1080 and 400dpi, rebooted. Now SystemUI crashes constantly and I can't do anything other than close the dialog window and use the power menu. Can't tap anything else (it shows Nova Launcher behind everything) and tried a USB mouse and keyboard via OTG, can't do anything extra with those. I feel like the keyguard is still on, but the same thing happens regardless of whether I do my knock code or a normal screen-on.
Safe mode doesn't help (other than disabling my 3rd party camera app allowing me to use the vol-down shortcut into the camera). I feel like if I could just get access to a root adb shell it would be pretty easy, but neither the stock recovery nor download mode allow for ADB.
I'd like to at least be able to pull smsmms.db so I can just flash back to stock and manually recover my messages.
(remind me to stop messing with things without TWRP or CWM or something...)
just ended up flashing back to stock and walking away with a lesson learned the hard way
Instructions on flashing back to stock?
Sent from my Nexus 5 using XDA Free mobile app
noutoo said:
Instructions on flashing back to stock?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2799647
scy1192 said:
http://forum.xda-developers.com/showthread.php?t=2799647
Click to expand...
Click to collapse
...or, just boot into stock recovery and factory reset (Power + Down(?) Button). Had to do this last nite when I over-froze in TiBu. Can't wait for custom recovery.
tbcpn said:
...or, just boot into stock recovery and factory reset (Power + Down(?) Button). Had to do this last nite when I over-froze in TiBu. Can't wait for custom recovery.
Click to expand...
Click to collapse
factory reset doesn't affect anything outside of /data, so it wouldn't have fixed my issue (I'm thinking the app I used put something in some sort of boot script since safe mode didn't work)
scy1192 said:
factory reset doesn't affect anything outside of /data, so it wouldn't have fixed my issue (I'm thinking the app I used put something in some sort of boot script since safe mode didn't work)
Click to expand...
Click to collapse
Yeah, I know that's generally the case, but in this instance it appeared to re-flash the entire /system...and, it wiped internal sdcard file, which is unusual, at least compared to "factory reset" in TWRP or CM. I'd inadvertently frozen a couple of critical system files in TiBu and bootlooped the phone.
In any event, solved my issue, but lost my TiBu backup on internal sdcard, which made for an extra couple hours work.