Related
So, after owning my Transformer Prime for about a month now, I decided to take the plunge and root it. I followed the instructions for ViperMod and had it rooted in no time. I then followed the instructions of unlocking the bootloader and finally installing OTA Rootkeeper.
I've had rooted devices in the past (Droid Incredible) and am familiar with RomManager. So I installed RomManager on the Transformer Prime. I then attempted to create a backup of my "current Rom", which is just stock ICS. RomManager prompted me to update Clockworkmod Recovery, which I did (I now have 5.8.2.0 installed). It then rebooted...acting like it was backing up my current Rom, but when I got back into RM, and clicked "Manage Backups" and there was nothing there. I tried once more with the same result, and ultimately gave up on backing up my current config.
I then downloaded Cyanogenmod 9 (nightly). I selected Google Apps and it proceeded to download. I got an error that the Google Apps portion had an error, but it seemed to work when I attempted to download it again.
I then proceeded to attempt to install the new Rom. The menu came up, asking if I wanted to wipe data and cache, wipe dalvik and backup current rom. I selected all three and hit ok.
My tablet rebooted...quickly, and did not show any signs of installing Cyanogenmod. Sure enough, I got my stock ICS...no Cyanogenmod. I tried again...same thing. I tried a third time, and RomManager hung when I tried to select Ok after the options of backing up, etc. Ultimately I got the error popup, asking if i wanted to wait/report/ok. I hit ok.
I then...very stupidly in retrospect...performed a factory reset from within the phone's settings menu (something I've later read is a big no no). This time, when my phone rebooted, it went straight into Clockworkmod Recovery, which is where I am now. Stuck. I've read a ton and tried everything but had no success.
Strangely, I can find the cyanogenmod file by navigating through "install zip from sdcard", then "choose zip from sdcard", then "clockworkmod", then "download", then "get.cm", then "get" and finally "update-cm-9-20120301-NIGHTLY-tf201-signed.zip". And it allows me to update using this file...even giving me the message "Install from sdcard complete"...but nothing happens. I'm still stuck in Clockworkmod.
If anyone has any advice, I'm begging for your help. Really hoping I didn't ruin my brand new tablet...
Thanks.
only thing rom manager is gold for on the prime at the moment is getting the latest CWM version. other than that, trying to flash a rom, reboot into recovery, or backup doesn't work in rom manager for prime. everything needs to be done through CWM itself. whether flashing a rom or making a nandroid backup. so you have to manually go into CWM and try flashing from there. did you make sure the roms were stored on internal memory to flash(I believe it can only be done on prime this way at the moment)? try a different rom as the CM9 has alot of bugs n issues at the moment. try flashing virtuous rom or a stock modified rom from developement.
also check out developement section for a thread called the Di's n Donts of unlocking and thread called how to or not unbrick your prime. answers you seek are in there.
See my unbricking thread
http://forum.xda-developers.com/showthread.php?t=1514088
Thanks so much for your help guys!
to demandarin: Unfortunately the only ROM I downloaded before everything went haywire was the nightly cyanogenmod 9 from yesterday. And as I explained, that ROM doesn't seem to be flashing for me... I've tried downloading other ROMs onto my SD card, but I can't seem to get my Prime to recognize the SD card in CWM, and I can't figure out any way to get ROMs onto my prime...now that its stuck in recovery. Do you know if I can load ROMs onto my Prime at this point?
to Diamondback: I read your unbricking thread and its given me some hope. It sounds like I'm falling into the "1a" category. I'll have to bunker down tonight and see if I can work through those instructions (I have no familiarity with ADB at this point, which is my main concern). Anyway, I very much appreciate you pointing me in the right direction.
I am curious though, is there some place I can look for clarification on what works in RomManager and what does not? None of that was made clear in the app itself, so I just assumed it was fully functional, like it was on my Dinc. Now I'm paying the price...
Thanks again.
original old thread on CWM on Prime...look through page and people state what works n what doesn't.
http://forum.xda-developers.com/showthread.php?t=1510983
new thread created today on a new updated CWM that should be used. has alot of issues that didn't mesh well with Prime and CWM fixed. seems like you might have jumped the gun a lil early. this is latest version thread. you can also get the latest version through rom manager.
http://forum.xda-developers.com/showthread.php?t=1533697
good luck!
demandarin said:
original old thread on CWM on Prime...look through page and people state what works n what doesn't.
http://forum.xda-developers.com/showthread.php?t=1510983
new thread created today on a new updated CWM that should be used. has alot of issues that didn't mesh well with Prime and CWM fixed. seems like you might have jumped the gun a lil early. this is latest version thread. you can also get the latest version through rom manager.
http://forum.xda-developers.com/showthread.php?t=1533697
good luck!
Click to expand...
Click to collapse
Thanks, but I actually do have the latest version of CWM (5.8.2.0), according to the link you provided. The thing is, I'm just very unfamiliar with CWM, or really any recovery software. The link you posted notes the following improvements:
-Possibly fixes bricks (by properly restoring boot.img)
-Correctly comes with Staging/System unmounted
-Nandroid Restores properly the boot.img (of backups created with this CWM). This means no more issues when restoring a Rom if you are coming from another from (for example, if you are restoring Virtuous after wiping cm9)
Which all sounds great, but I have no idea how to really use any of that... Does "possibly fixes bricks" apply to my situation? I've tried selecting restore and advanced restore through CWM, but in both situations it says "cannot find files", which I'm assuming are the "boot.img" being referenced. So again, it seems like I'm hosed...
I'm just really hoping that Diamondback's unbricking method works for me. Though, I'm having a hell of a time finding instructions on how to setup ADB on my PC (Windows 7). Do you know where I can find good and current instructions?
you can Google it but plenty of YouTube view on how to set up adb.
there's a thread here on it though. take a look: http://forum.xda-developers.com/showthread.php?t=1427008
demandarin said:
you can Google it but plenty of YouTube view on how to set up adb.
there's a thread here on it though. take a look: http://forum.xda-developers.com/showthread.php?t=1427008
Click to expand...
Click to collapse
Thanks again! I think I need a tutorial on how to search XDA more effectively
SUCCESS!
Well, it took some jumping through hoops, but once I got ADB set up successfully, Diamondback's instructions worked like a charm!
For anyone encountering this thread with the same issues as me, I've included links to all of the sources of data I ultimately used.
Thanks so much for everyone's help!
Installing ADB
http://forum.xda-developers.com/showthread.php?t=1427008
http://www.youtube.com/watch?v=ZY4KSrgi-rE
I had to use the PDANet method, referenced in the Youtube video
http://junefabrics.com/android/download.php
Diamondback's Instructions for Unbricking the Prime
http://forum.xda-developers.com/showthread.php?t=1514088
Perhaps I spoke too soon...
My device is no longer bricked, but now I can't access CWM, can't factory reset...can't do anything. I'm stuck with a very broken build of Cyanogenmod 9
Here's the link to my new thread:
http://forum.xda-developers.com/showthread.php?p=23349041#post23349041
[FIXED]
Got some help on the forum;
downloaded asus firmware, unpacked blob, fastboot flash staging blob; fastboot reboot
Prime is now back to fully operational!
Many thanks to @kkdm
[/FIXED]
Hello,
I have looked around the various threads (including the 'how to unbrick your prime' one) but have not seen this issue mentioned.
I have a strange issue where if I factory reset (i.e. to Asus) the device will simply keep looping at the ASUS EEE logo, with device is unlocked in the top left hand corner. If however I install CM10 or another MOD, it seems to work as normal and boot into the homescren.
Having read around, there was an issue with an Asus update where it appeared to do something similar to this, is it perhaps that I am on that version and thus am getting the same error? Would a simple download and copy of the latest ASUS ROM fix that? I am unsure on how to do this exactly, but have read this was an issue, but I find it unlikely as everything was fine before I unlocked etc.
Is it perhaps the bootloader has become corrupt in some way with the ICS/JB difference? This is just a guess on my limit knowledge...
The reason for putting back the ASUS stock ROM is selling the device, having upgraded to the Infinity, and do not particularly want to send it with CM10 on.
Any help would be greatly appreciated,
What do you mean factory reset back to asus ?
You cannot just hit factory reset and it will go back to stock rom as you have overwritten it with cm10, or do you mean you have tried to install the stock version of the rom?
DO NOT use the official software from the Asus site, this can brick it.
There is a stock rom somewhere in the development section. You need to flash that to the tablet and you will be good to go.
edit... this is what you want .. http://forum.xda-developers.com/showthread.php?t=1708613
It turns out there is no ROM on the internal storage anymore (I must have selected the format option on my last attempt at installing Androwookie), as a result I cannot access the sdcard by plugging the thing into my PC.
Is there a way of installing this via the micro SD card slot?
flumpster said:
What do you mean factory reset back to asus ?
You cannot just hit factory reset and it will go back to stock rom as you have overwritten it with cm10, or do you mean you have tried to install the stock version of the rom?
DO NOT use the official software from the Asus site, this can brick it.
There is a stock rom somewhere in the development section. You need to flash that to the tablet and you will be good to go.
edit... this is what you want .. http://forum.xda-developers.com/showthread.php?t=1708613
Click to expand...
Click to collapse
Hello,
Just to clarify, I can get into recovery without issue, it just won't boot after factory reset and now hangs at ASUS logo.
Is there a way around this at all? :--(
Hello,
Latest problem is having ASUS Transformer Prime ADB Interface listed in Device Manager, but not being able to use the adb shell.
I get either 'device not found' or occasionally something about /system/sh not being found, in either case this is obviously not good.
I can still get into TWRP 2.1.3 though, surely there must be a way round this?
Now fixed, see first post
Hello, all. First, I'd like to say thank you for taking the time to read this and potentially try and help me out. Any assistance with this matter would be greatly appreciated!
I added the (Non-standard) to the title, as I've been flashing and modding this phone for over two years, and I've never experienced this issue. I'm not the type to ask for assistance, as my research skills are well above par, but after digging through literally countless forums and topics, I have yet to find anything quite like my situation...
ISSUE: Performed recent flash attempt to epinter's CM10.1. Now loads to Moto splash, sits there the usual few seconds, but when it comes time to load the rom, it reboots and starts the process again... (I swear I think I see it trying to load the rom splash for like a micro second, but then it could just be the delirium of long hours researching and fighting this problem.) Now, you might be thinking, "Eh, pretty common...", right? Yeah, me too, until I couldn't fix it like I've done a million times before... I can boot into recovery. I have performed ALL standard actions regarding flashing a new rom, yet the problem persists. The problem persists now no matter what rom I attempt to flash. Now you might be thinking, "Just flash your nandroid recovery...", but I wish, oh how I wish I could... I am currently using CWM-based Recovery 5.0.2.7, although I've tried more than a few different recoveries since this issue, all provide the same results... Which is nothing. I'm at the end of my rope here.
I've even tried flashing TWRP (two different versions) so I could at least get some charge to the battery so I could continue this debacle, but it hangs at the TeamWin splash screen...
Fastboot loads fine. Wipes performed to system, caches, partitions, etc, to no avail... Battery pull, already tried...
I've covered all the basic fixes, but my issue seems to be bigger than my knowledge base (at the moment).
Okay, here's the exact details of what led up to this...
My Atrix WAS unlocked, rooted, and using RR's CWM for recovery at the time. I had flashed everything coming and going as the scene grew, but eventually went back to CM7.2 and had been running it for ages. Well, I decided to try something new, and settled on trying BeanStalk. Flashed Aroma Prep, no problem. Flashed ROM and Gapps, no problem. Booted up fine. Decent start on the rom, but a little too buggy yet for me. So on this note I wiped and restored my CM7 nandroid backup, no problem. All was well, until I came across epinter's CM10.1 and thought, "Eh, why not?" (...and now look at the mess I'm in!) Performed a new nandroid backup of my CM7, and began the process that ended me... Everything went along just fine. Performed all my wipes, flashed my zips, rebooted, and BAM... boot loop! Little did I know what kind of headache I was in for, until I couldn't restore my backup. Now, I'm just praying I find a solution before my battery drains out completely...
SIDE NOTE: While attempting to restore fails and just resets recovery back to the main screen, there are no visible errors reported. Attempting to flash ANY of my other roms results in the same behavior. Flashes "appear" to go smoothly, but the end result is the same... I did notice upon attempting to flash BeanStalk again that there is an error reported in the aroma installer. It performs all wipes correctly, but when it comes time to actually install, it reports a broken symlink error, or something to that effect... (I would reproduce the install error message, but at the moment I'm trying to hang onto as much battery life as possible. My apologies for the inaccuracy of any statement.)
PLEASE, LADIES AND GENTLEMEN, I BEG OF YOU... If anybody has been unfortunate enough to have found themselves in my shoes, then hopefully you were lucky enough to get it figured out by now and would be willing to pass along the info. Although not my primary phone anymore, it still gets more than it's share of use. I'd hate to see it go out this way...
Any help to guide me in the right direction would be most appreciated! Thank you all in advance!
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
vagfyt said:
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
Click to expand...
Click to collapse
There's an issue with SuperSU when it tries to install in systemless mode.
Flashing it this way seems to do the trick, and has been confirmed by multiple users on this board: http://androiding.how/root-moto-g-2014-marshmallow/
If you're using CM13, there is no need to flash SuperSU. CM13 has its own root pre-installed, you can turn it on in Developer Options.
Hi!
Finally I got stuck in a boot loop on my Pixel 6 running QPR2.
It's looping after the G animation (vibrates a few times at that point when attached to a PC).
Reflashing the latest QPR factory image (without -w) by using SDK 33.0.3 does not solve the issue.
The ROM was running fine before, but it rebooted due to a faulty custom kernel version and now I'm stuck.
My theory is, that the launcher (nova) can't load and therefore it reboots.
Anything I could do using fastboot?
Never flash a custom kernel on a stock ROM, If not suggested by the dev.
I understand that you flash without wipe?
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If the kernel broke your actually ROM, nope. You could backup the file stored locally via adb in the recovery, but not anything more.
Wipe all is the best, better than have to handle with an hard brick.
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If I were you I'd maybe get some logs and go through them and see if you can find anything that way. Maybe add logs to your op here.
There aren't many ways to backup things nowadays for pixel 6 but what I have used to backup apps + app data that works well when restoring is Neo app from Fdroid store. As far as backing up goes, at this time I've used nothing that is/has been as solid as Neo. I miss the days of just being able to boot one of a few various custom recoveries, making a nandroid backup to a USB thumb drive with my OTG cable and restore it whenever it was needed but things change. Sounds like maybe something was left behind from your kernel install. If you really dislike formatting I'd stay away from whatever you installed here to get in this loop but definitely backup using Neo once you get going again and put your backups on thumb drive or you PC or somewhere other than your device so you can restore them when you need to. I don't flash nowhere near as much as I used to but I used to flash my device(s) many times a day , everyday for many years but I remember years ago on another device I looped and wiped my cache and system and reflashed rom and ended up booting up. But that was another device years ago. Maybe try adb sideloading instead of factory image flash without wiping data. Try that and after it's done installing reboot to others slot and sideload it again... These things probably won't work but you never know until you try. Did you have magisk installed before and not now? Maybe flash stock kernel patched with magisk to both slots if so. Hate to say it but you will probably end up having to format data but idk because I don't know exactly how you installed the kernel "in detail" or exactly what kernel it is or if anything else was changed from before you looped ... No logs...
I've been using Android since the beginning (G1) and I've been tinkering with my devices since back in the Nexus S days on a regular basis and I've found that the best way for to get the help I need is to try like hell to figure whatever it is out myself by searching for the problem I'm having, I mean like really searching, sometimes for hours , sometimes maybe searching for things related to the problem I'm having that show up in my searches, sometimes the answer can be in another devices forum, piecing together bits of info from various places to try and solve whatever it is... etc ... etc... But the best way to get help is do research on it, take some notes, try various things to fix it, then if I still can't figure it out make a post about it here and in op attach every log I can possibly gather from said device, include all the things I tried to fix it with myself "in detail..." My exact installation process, you know like: reboot bootloader, was on slot A, executed ./flash-all.sh for factory image xxxxx, rebooted system ... The more details you provide the more accurate people will be when answering and the more people you will get to reply.. I'm not trying to sound like some asshole or anything at all. Im just speaking what works best here to get answers. Sometimes you just don't get any answers even if you post 18 paragraphs with a chart and a line graph, things you tried, what all you tried it with and links to it all. But anyone here who does this will most definitely stand a much better chance at getting some replies on whatever it is. I sometimes read over on Reddit and Tele groups , sometimes answers can be found that way. Sometimes people just give you the silent treatment.. Even if you do your homework. That's just a thing with anything related to development that happens. I always used to think when I would get no replies that the other guys and gals who know the answer are thinking to themselves, "oh look at this idiot here!" "He clearly didn't graduate from Harvard top of his class with a PhD like we did. " " Such an imbecile!!! " But what could have been going on and more than likely was/is is life , kids, bills, sleep, relationships, covid19, and tons of other things..
Some of this development stuff is a real beech to get and everyone works hard to get it and many aren't too fond of just giving random people answers that took them many sleepless nights to get. But if and when a dev sees someone with a detailed post , things tried.... etc ... etc .. Theyre much more likely to throw some knowledge your way. That's been my experience anyway.
@flash713
Wow, thx for thw write up, appreciate!
I was on latest QPR2.1 with Radioctive Kernel, Magisk installed.
Since the device got stuck in the boot animation, I tried a lot and flashed different factory images using the flash-all method. w/o success.
Also tried the Flash tool in the google website, also w/o success.
When the device boots while it's connected to the PC, it beeps/vibrates 3 times and the reboots.
My guess is that it has problems to load the launcher, Nova was set as standart.
I'm using android since years, tinkering a lot, but I'm not a pro in doing so.
Meanwhile i set up my new Pixel 7 and restored it via Google backup and a few apps by using a SWIFT backup.
Fotos were restored by Google, but all whatsapp pictures are messed up ow, cause the date of restore.
How do I gather proper logs?
Did a last attempt and sideloaded the OTA to both slots...same outcome...
Doesn't magisk have a remove all modules.zip? I mean oriole doesn't have TWRP available yet.
I presume that when it's bootlooping you don't have any ADB?
You did have ADB enabled, right?
Depending on system and setup you may have ADB started by init or started by Android.
Your problem could be as simple as a bad Launcher.
I don't know if the P6 has a UART console. Does it?
Hi Renate,
thx for your reply.
Yes, that is what i thought. The Pixel boots up into the G-animation and then loops 3 times (beeping/vibrating if connected to PC) and than reboots in total.
I think I had something like that in the past when I accidently deleted the launcher apk (don't ask )
Anyway, Nova launcher was set as standart, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Sui77 said:
Anyway, Nova launcher was set as standard, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Click to expand...
Click to collapse
I'm still not clear if you have ADB ever available.
If you do you could:
Code:
adb uninstall com.nova.whatever.launcher
If the /data/data that Nova is using is corrupt or missing it could cause failure.
Android will switch to whatever else belongs to android.intent.category.HOME automatically.
If there is nothing there you can install another launcher.
Have adb (after booting into recovery mode), will report back asap
I habe adbd device connected via recovery/rescue mode, but that's not working.
In bootloader, I can't use adb, no device connected.
Hw can I use adb while the device is not booted up?
Can you mount data in recovery (and it's unecrypted)?
Feeling a bit dumb, but I can only boot into fastboot or into the boot loop, don't know how to mount data in recovery mode (the one with the andoird robot)
When you're in the boot loop you don't get adb even for a few seconds?
This are the last lines of the recovery.log
2 new items by TheMrSui
photos.app.goo.gl
Checked that by opening a cmd and using "adb devices", but nothing showed up
When you're viewing that log, don't you have ADB working then? It says that it is.
I had this weird issue on Raven, first try using android flash tool through a chrome based browser. If that still loops then wipe, and flash an older image. For some reason I had to flash an image from the previous month and that would boot.