Hi there,
I just read a lot of threads in this section, but it realy seems as nobody was as stupid as me.
Today I decided to root my Prime and it was all simple.
I used vipermod to root, unlock and install cwm.
I made Titanium Backup of all my Apps (nothing important here), and made a backup via cwm.
With cwm I flashed Virtuous Prime and all was fine.
Then I made the big mistakes:
-I restored most of the apps with Titanium Backup.
-I used a code to unlock my prime and I also wanted to test the encryption.
After the reboot that comes after the encryption, I entered the key, and the Prime booted.
As the lockscreen appears I entered my lockscreen code (which is the same as the encryption code) and it was ... wrong!
I don't know exactly how this happend, but maybe it was due to the Titanium Backup that I restored. Maybe I restored a system app which included the code?! I don't know.
So I couldn't enter my device, but I still had cwm, so I thought this wouldn't be a problem.
I thought I could do a factory reset, and all would be ready to go.
I did a factory reset, wipe cache, wipe dalvik - nothing helped.
It was a problem, because cwm didn't let me do anything, neither restore my backup (not found, because encrypted) nor flash the ROM again (the same here).
The only thing left I tried, was formating all the things, that I could format, but this sucked me even harder in this desaster. Now my Prime got bootloops and I don't know anything to do.
Any ideas or help is apreciated!
I would thank you so much, if anyone could help me get my Prime back to me!
have you tried to adb into your device from a PC? there's a thread in developement section called do's n donts of unlocking. I think it tells you in there how to get out of bootloop.
Thanks for your answer!
You mean this, right?
Seems as I'm nearly at Brick 2, even if I don't get "unrecoverable bootloader error", but my Device also hangs in this splashscreen with the "Eee Pad" in the middle.
Looks like I'm lost
Edit: Needed a bit to get familiar with adb, but I was able to push the rom again on the sdcard.
I fullwiped and installed the rom. First reboot askes me for encryption code, then the rom needs a bit to start.
Problem remaining: The code on the lockscreen is still wrong. I can't enter my device
Is there there any possibility (if even a full wipe doesn't help) to get back to my device?
Solved: I just had to wipe via the boot menu (voldown + power button, then wait the 5 secs)
Encrypted partition has gone!
Related
I have finally got my phone unlocked and rooted. Now I am trying to install the quicksense ROM. I know I am doing something wrong, because all I get is the white HTC screen at start up, and thats as far as it goes. So, here is what I did, and maybe someone can help me out.
I downloaded amazing quicksense and dragged it into my sd card
I booted into recovery
I did a backup
I wiped the cashe
I went to install from sd card and chose the zipped quicksense file
I then got install from sd card complete
I then went back and rebooted phone
From here the phone freezes on the white HTC screen and does not fully boot.
I had to go back into recovery and do a restore to get my phone working again.
What am I doing wrong. Please help.
Seem like you did succeed at everything except the cleaning parts
Please try again by going into recovery and
1. wipe data/factory reset
2. Wipe cache partition
3. Go to Advance then wipe dalvik cache - after that, choose go back
4. Install rom from sdcard
5. Reboot
I will try and do what you have instructed. However I wanted to ask one question before I do this. In your first step to "wipe data/factory reset", will this reset my phone back to factory, essentially wiping all my data and everything I have on it? I know unlocking the bootloader did that, but it would suck if I had to do this every time I installed a ROM. Just want to make sure what I am up against. Thanks
ms2knights said:
I will try and do what you have instructed. However I wanted to ask one question before I do this. In your first step to "wipe data/factory reset", will this reset my phone back to factory, essentially wiping all my data and everything I have on it? I know unlocking the bootloader did that, but it would suck if I had to do this every time I installed a ROM. Just want to make sure what I am up against. Thanks
Click to expand...
Click to collapse
Hi
I am by no mean a dev so my advices is more like ... well, advice - not instructions my friends
Wipe data/factory reset mean wiping every personal datas that you had on the device and yes, this will reset your phone back to the present rom that you had on the device - in your case is the stock/factory/carriers rom.
Every time you install a new rom you should - and every dev will suggested this - wipe clean your data and whatever info that may still left on the device from previous rom - you may not need to do this when you update to the new version from the same rom. Sometimes the new version of the same rom featured too many changes then the dev will instructed user to wipe all the data. That's why we user should always read the first, second and third post to make sure we keep ourself up-to-date when flashing rom.
Personal data means your google account, emails, contact list, SMS, wifi password, bluetooth pairing and apps setting ... However, we can backup and restore most of these info using diferrent apps. Here are some app that I found helpful in term of backup:
* Gmail account for contacts list
* SMS backup for SMS and call log
* Titanium Backup for apps and it's data: This app is very useful, for example if you use it to backup your email app it will included your setup and password ect ... so after install new rom and restore a particular app, you have an option to restore the app plus it's data or data/app only
Read this thread for some useful tips on how to using Titanium Backup
http://forum.xda-developers.com/showthread.php?t=1324291
Googd luck and welcome to the Amaze
I really do appreciate your advice. I will go ahead and backup everything, and then attempt the ROM install again. Hopefully it will work this time. Again thanks.
Not a problem mate
Since you already backup your rom and QuikSense is a Sense rom anyway, it doesn't hurt to try restoring data from the backup. You can do this (after finish flashing the new rom) by go back into Recovery/Backup and restore/Advance restore/choose the backup file (in case you have more than 1 backup)/then chose restore data
I did this when switching from QuikSense rom to Senseless Rom and it work flawlessly
Worst case scenario is you will have to restore again. This will save a lot of steps.
ms2knights said:
I have finally got my phone unlocked and rooted. Now I am trying to install the quicksense ROM. I know I am doing something wrong, because all I get is the white HTC screen at start up, and thats as far as it goes. So, here is what I did, and maybe someone can help me out.
I downloaded amazing quicksense and dragged it into my sd card
I booted into recovery
I did a backup
I wiped the cashe
I went to install from sd card and chose the zipped quicksense file
I then got install from sd card complete
I then went back and rebooted phone
From here the phone freezes on the white HTC screen and does not fully boot.
I had to go back into recovery and do a restore to get my phone working again.
What am I doing wrong. Please help.
Click to expand...
Click to collapse
How long do you wait?
The first boot may take several minutes.
Do you have adb installed on your computer? If so then from the command prompt (or terminal if your running Ubuntu) type "adb shell logcat" and if it seems like it's repeating itself over and over again then your caught in a loop and would probably just need to clear the data and caches. Your problem should clear right up.
Binary100100 said:
How long do you wait?
The first boot may take several minutes.
Do you have adb installed on your computer? If so then from the command prompt (or terminal if your running Ubuntu) type "adb shell logcat" and if it seems like it's repeating itself over and over again then your caught in a loop and would probably just need to clear the data and caches. Your problem should clear right up.
Click to expand...
Click to collapse
To be honest with you, I did wait for maybe 5 min or less. I guess I thought it would boot normally. I will try again and give it some time.
Being very new to this, I am trying to learn all of this. How do I know if I have adb installed on my computer? Thanks
ms2knights said:
To be honest with you, I did wait for maybe 5 min or less. I guess I thought it would boot normally. I will try again and give it some time.
Being very new to this, I am trying to learn all of this. How do I know if I have adb installed on my computer? Thanks
Click to expand...
Click to collapse
Follow the instructions on this thread here:
http://forum.xda-developers.com/showthread.php?t=928370
Easiest way to set up ADB.
Hope this helps.
Well, I finally got it to work. My probem was that my sd card was not FAT32 but FAT. I think this was the problem I had with trying to flash clockworkmod. I did everything except the wipedata/factory rest, to see if it would work. And sure enough, I am now running Amazing Quicksense 1.5.1. Thanks for every ones help.
Transformer Prime - Unlocked Bootloader -Settings - Backup & Reset - Factory Defaul
Although im an expert in adb, roms, and android sdk development, because i dont normally contribute, im a "noob" and cant post in the development section???? Whatever, his my community contribution.
I rooted my Transformer prime, and unlocked bootloader. I held off on installing custom roms because i wanted something iron clade.
Also, had problem booting into CWM after bootloader unlocker.
I do however enjoy wipping my prime ocassionally to get a fresh install due to security fears such as installing software from outside the marketplace
So one day, after rooting and unlocking bootloader, i reset the prime to factory default.
Problem:
Factory default reset erased user data
Reinstall of this data on reboot was blocked from installing, because CWM kicked in and saw it as a wipe of data. Result, infinite bootloop into CWM which i couldnt reach before. Since the command inside the android os was never completed because of CWM, i couldntboot os.
Did i mention i never made a backup before the issue occurrered??? Ekkkk
Steps to repair:
-immediately create backup of what is still installed on prime in CWM.
-adb push a rom found on xda developers for an additional avenue of restore in the event your backup from the proceeding step fails. Adb can be a pain, if its not working, abd stop-server and thenre-push the rom to / directory, not /sdcard
-format all partitions available in CWM. Including stagging...
-restart device
-use fix 1a located here http://forum.xda-developers.com/showthread.php?t=1514088 careful with command entries, if your using windows these commands are like sudo to your device. Thanks to the genious who came up with this.
-once completed, restore your stock backup. Then make a new bakup of your fixed stock rom. You shouldnow be able to boot your stock rom and you have a backup. If not, erase everything again in CWM and installu the additional backup rom from step 2 (any rom is better than none).
Done. Restart and pad yourself on the back. You just brought prime back from the dead.
I thought it would be good to share as no one has addressed a fix from a problem caused by a data wipe factory reset on prime done inside the os.
Sorry for type ohs, i suck at typing on my tablet.
Wave, on his revived Transformer Prime
P.S. this method will also work when dealing with a bad OTA update from asus, providing you can still adb the latest CWM, boot CWM, and have rom to restore. Im buying bricked primes to resell working contact me for repair service
Finally used the Full Wipe Tool from the Transformer Prime. This tool works everytime, but it does have issues with improper file structure after using preventing you from pushing a rom via adb. The best work around, after using the tool, reboot, hold down volume button but don't hit up. wait until it boots to the Full Wipe, USB, Cold boot options. Select Full Wipe, let it wipe the system. It will repair the file structure. Reboot back into CWM, create a backup. You can now adb a rom to the sdcard. Works like a charm everytime.
I love this tool, I get that fresh install taste everytime I install a new ROM.
Link to full wipe tool I was talking about above
http://forum.xda-developers.com/showthread.php?t=1670824
Works awesome when using this technique above. The technique above is the perfect work around for errors transferring, include protocol errors in Windows, and if you are transferring using adb, but after the transfer cannot see the file transferred on the Asus Transformer Prime.
I'm beginning to think this tablet is unbrickable, unless you are really, really, dumb and flash an original OTA update.
You saved my bacon, I just used the superwipe script and am having issues with pushing a rom. Thanks a ton.
Edit: Or not....Can't get the Prime to show up when I use adb devices...
Hello,
If anyone could help me get my phone back into a functioning state, I would very much appreciate it! I have been playing around with the Cyanogenmod 10 nightlys. All was going well until I decided to try encryption. It encrypted the phone okay, but I decided to format the phone and get it back to an unencrypted state, except it wouldn't allow me to factory reset. The button to start the reset did nothing except reboot the phone a few minutes after pressing it.
No problem, I thought, I made a nandroid backup before I started playing with ROMs, I'll just restore that, except that didn't work because CWM couldn't mount the encrypted volumes. So, I copied the CWM backups to an SD card using root explorer, and tried to restore from there. It gave me an error advising it couldn't mount/format /system. So, I rebooted, only to get stuck on the Samsung boot logo.
I can still get into download mode though. so I tried flashing the stock firmware with Odin. Odin reported the software flashed succesfully, and the phone boots now with the stock animation so presumably it did work, but it still asks for the encryption key. I put in the key I used originally but it rejects it.
I don't know what else to do to restore my phone to a stock state.
This is my first Android phone and I was just playing around out of curiosity, so pleas excuse any noob errors I may have made along the way. I shall be sure to learn from them.
Please tell me I can get my phone back to the original state!
s0mmie said:
*snip*
Click to expand...
Click to collapse
It seems I have managed to get back to a working state by using the Android recovery menu. Phew. I shall not be messing with encryption again. All part of the learning curve though, I suppose!
Hello community
sorry for bothering, but it's two days I'm stuckl with a problem and... zilch.
last day my phone, an O2 Galaxy Fame, ran out of battery (damn me) and decided finally to enter perpetual bootloop. Sometimes when rebooted took like 2, 3 hours to get out of the loop, today it's already 24 hours and more of bootloop. I can log into the recovery system (CWM, installed today in a desperate try to gain root access).
I would like to perform a reset, but doing so I would lose all the details of the Exchange mail and the wireless setting. that wouldn't normally be a problem, but tomorrow I'll be outside the country for a 3-day meeting and I'd need to read the mail. and configure the phone again, that is; is there a way I can force myself into the phone, gain superuser access and retrieve the files I need? I can read and understand adb shell commands, I'm not completely noob on linux and can follow guides.
There is so much mess in the android rooting - IMHO. at this moment I'm stuck with "adb cannot run as root in production builds" and can't sideload Superuser.apk from the recovery sideload screen.
If you could help me before tomorrow it would be great!
thanks!
Seems like a bit of a tough spot there. So it seems like you won't be able to access root that way due to the kernel blocking it. You'd essentially have to have to split the kernel, then decompile the ramdisk and edit default.prop and change ro.debuggable to 1, then recompile and flash the kernel.
So the phone goes into bootloops whenever it runs out of battery? Seems like kind of a big design flaw or a serious bug. Since you now have CWM, you can try and just see if clearing the cache and dalvik cache + fixing permissions might help. Won't make it any worse and won't wipe any important data. Other than that, maybe see if there is a stock rom that's exactly the same as the version you have and flash it over top of your current set up while wiping the caches. If that doesn't work, then you can try to wipe the caches and /system and reinstall Only do this if you know the rom works or you have a way to reload it completely via the PC - so this is a last resort because without /system, you have nothing to boot to!
I've no way to test this, but with most devices, if you have CWM installed, you can flash the SuperSU zip from Chainfire to root the device ( http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip ), but this will not necessarily allow you to do anything in recovery still if the kernel does not let you mount adb via root without making the other changes.
thanks, I've returned today from the business trip but since there is no IT today, this leaves me some more time to try with what you said - I'll let you know how goes.
Well, SuperSU loaded and for a brief second a "apps are starting" popup came out. Better than nothing!
but I'm stuck into bootloop as well.
My tought is: if I flash the same android version on the phone again, won't this delete the /data folder as well?
...I came up with one thought: there isn't any recovery distribution acting as a full android? can I trick android with Odin installing android on the recovery partition, so that it boots into that, and from that with su powers recover what's left in the "main" area?
I'm thinking it as a hard disk with two main partitions, one with android and one with a recovery system.... tell me if I'm wrong.
no one helping?
at least explining why?
Hi guys!
I somehow messed up my system with LSPosed in Gravitybox. A conflict made my phone unworkable (screen just kept flashing). No worries since I kept a Nandroid. After just putting this back (I ticked literally ALL the boxes) my phone goes trhough the OnePlus-loader (dot turning into square) and then says only "turning off" in the screen. Nothing else works. So I can only re-access the device via PC-Terminal in TWRP.
Fact is... Nandroid was taken BEFORE LSPosed was installed, Nandroid gave no errors when taking and gave no errors when "putting back". But device just kind of softbricks AFTER boot. Very strange. Any ideas?
Could it have to do with DM-Verity?
Just wondering: did anyone actually MAKE a NANDroid (ticket all the boxes) and tried to put it back? Questions:
- when putting it back: do I need all the boxes ticked, or just a few?
- when making a NANDroid - do I need to disable PIN, fingerprints etc.? Or can it stay active?
- did anyone succeed so far? - I am wondering why mine doesn't work?
Please share your experiences!
Can confirm neither my Nandroid backups are working.
Dunno if any security pin or measure needs to be disabled first, but it shouldn't.
So far, the most safe way I've found to make a full device backup, is through adb:
While booted in TWRP use the adb commands:
Bash:
adb shell
ls -la $(find /dev/block/platform -type d -name by-name)
to list all partitions.Then you can use
Bash:
mkdir /sdcard/PartitionsBackup
dd if=/dev/block/sdc"partition number" of=/sdcard/PartitionsBackup/"partition name".img
to backup every partition in your internal storage.To flash them back you can use fastboot:
Bash:
fastboot flash "partition name" "partition name".img
# Example
fastboot flash boot boot.img
Wow, that's is almost out of league for me :-(
Anyone can help fix this? How is everyone doing?
Can anyone help me in overcoming that kind of a problem .?
I've tried recovering with TWRP, I suspect the problem there is encryption, because when I factory reset the data, I can start fresh.
If you just want to have a working phone, try doing a restore and factory reset (also try reformatting the data partition if a factory reset does not work).
Just let us know if this worked for you.
exis_tenz said:
Wow, that's is almost out of league for me :-(
Anyone can help fix this? How is everyone doing?
Click to expand...
Click to collapse
I've created a Tool that could help, if you're still able to backup the original working firmware.
Anyway, I personally suggest to go with multiple type of backups (TitaniumBackup + Nandroid + PartitionsBackupper) first.
And when it's time to restore, wipe everything with the stock recovery and start fresh. Restoring the userdata partition for last, checking if everything works before flashing it.
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
exis_tenz said:
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
Click to expand...
Click to collapse
If you backup everything before hand (IMEI partitions included), you can pretty much wipe anything without worries (by personal experience at least).
To revert back to stock you can easely flash the stock boot and stock recovery partitions via fastboot.
Or, in case you just want to backup them, just download them directly without need to touch the phone.
Raygen said:
If you backup everything before hand (IMEI partitions included), you can pretty much wipe anything without worries (by personal experience at least).
To revert back to stock you can easely flash the stock boot and stock recovery partitions via fastboot.
Or, in case you just want to backup them, just download them directly without need to touch the phone.
Click to expand...
Click to collapse
As i always say: Dont flash around without backups
exis_tenz said:
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
Click to expand...
Click to collapse
4th factory flash???? I think u shouldnt flash somerhing anymore
Well, when I started with this phone, I made a NANDroid of stock rom, just plain, rooted. During the adventure setting it up, I kept making NANDroids.
Then when I was done (phone in use for 2 days) I installed LSPosed and Gravitybox. WARNING: if you mod the clock position in Gravitybox to middle: your phone will not work anymore (some framework error I guess). Then I decides to put back a 2 hours before made NANDroid back... Which got no errors when making and none when putting back... But the phone bootlooped. Actually it started through the loader, started Android and then only showed "switching off" in the screen. Which it didn't.
Then I needed a factory flash. The first factory flash gave me a "serial nummer incorrect", the second one a battery drain (no sim, wifi and bluetooth off, lost 50 percent battery in 9 hours without finding out what caused it). The next factory flash worked without the serialnumber error but also gave the battery drain AND did not let me enter a pinlock neither a fingerprint.
So tomorrow we'll try again.
What I noticed that even when a factoryflash @oneplus servicepoint was done... Some data survived (!) in the phone (which shouldn't). I still had a TWRP-folder there so I guess it's like more junk just survices. That probably causes all the trouble.
It's time OnePlus releases the firmware!
I've been in the same situation (even twice ) For me just deleting the Gravitybox.apk from system folders did the job.