I had a rooted AT&T play, rt800at. I recently installed clockwork mod recovery without unlocking the bootloader using the new method in the development section. I then backed up my stock image and downloaded and attempted to install the GSX ROM. I wiped userdata, and cache (including dalvik) before trying to flash the ROM. Now when I start up I get the Sony Ericsson text and the phone hangs there. I can't get back into recovery to restore my nandroid backup. What can I do?
Check in the cwm thread ; i also had a similar brick ; how i fixed it is in the thread in the first few pages i believe.
This one? There's nothing about a brick here though... http://forum.xda-developers.com/showthread.php?t=1130639
No , this one .http://forum.xda-developers.com/showthread.php?t=1390771
Here's my post on how to fix it :
Retrying on SEUS(Sony Ericsson Update Service) several times. NOTE - This means pressing the retry button when it says you have failed ; not closing the app and opening it again - I did this as well and it didnt work.
Thanks for the info. However I already fixed it a different way.
I basically just stumbled around, but this is how I did it:
The phone wouldn't get into recovery, so I couldn't restore the backup I made just before I started screwing around with it. To get around this I used flashtool to flash a random stock .ftf, then rooted that and used the method to install CWM without unlocking the bootloader. All I had to do then was reboot into recovery and restore my backup.
Related
Okay so last night I was putting on a new theme on my phone(MT3G/32B/T-MO Branded).
After applying the update, rebooted and it started to hang. Tried running one of the nandroid backups that I have saved and it booted backup but all sorts of processes kept force closing, not allowing me to do anything.
Tried a few more nandroid backups, with same results, so I decided to flash the stock firmware back on. So I put the sappimg.nbh file on sdcard and updated it with that.
Now the stock image ALWAYS works with no problem. It lets me flash a new recovery image with Recovery Flasher(Tried Rav 1.2 and CM-1.4). Both recovery images work but when trying to update with a new rooted rom it sits at the first splash screen forever. I've tried a few roms like CM-4.0.4 and 4.1.11.1.
By this time i thought maybe the roms were corrupt so I downloaded a new CM-4.1.11.1 and it took a while but it did boot up, but once i put in my log in info it just froze on the home screen. Rebooted and stuck at the first splash again.
Remember how I said I reverted back to stock firmware? well once I did that and after all this trouble, I tried running a nandroid backup and no matter which one I run, it being and old one or if i just make a new backup they all come out with the same error: "Nandroid failed:run "nandroid-mobile.sh restore" from adb.
Any ideas??? At the moment i'm downloading CM-4.0.4 to try that because i've had problems with 4.1.11.1 and flashing that without having 4.0.4 already flashed. So i will try 4.0.4 right now, hopefully it works and if it does I will update to 4.1.11.1
Thanks guys, first post so don't be too rough...
my experience with that is solvet by booting recovery ROM from say raon and choose wipe data, then reboot
lupascu.marius said:
Okay so last night I was putting on a new theme on my phone(MT3G/32B/T-MO Branded).
After applying the update, rebooted and it started to hang. Tried running one of the nandroid backups that I have saved and it booted backup but all sorts of processes kept force closing, not allowing me to do anything.
Tried a few more nandroid backups, with same results, so I decided to flash the stock firmware back on. So I put the sappimg.nbh file on sdcard and updated it with that.
Now the stock image ALWAYS works with no problem. It lets me flash a new recovery image with Recovery Flasher(Tried Rav 1.2 and CM-1.4). Both recovery images work but when trying to update with a new rooted rom it sits at the first splash screen forever. I've tried a few roms like CM-4.0.4 and 4.1.11.1.
By this time i thought maybe the roms were corrupt so I downloaded a new CM-4.1.11.1 and it took a while but it did boot up, but once i put in my log in info it just froze on the home screen. Rebooted and stuck at the first splash again.
Remember how I said I reverted back to stock firmware? well once I did that and after all this trouble, I tried running a nandroid backup and no matter which one I run, it being and old one or if i just make a new backup they all come out with the same error: "Nandroid failed:run "nandroid-mobile.sh restore" from adb.
Any ideas??? At the moment i'm downloading CM-4.0.4 to try that because i've had problems with 4.1.11.1 and flashing that without having 4.0.4 already flashed. So i will try 4.0.4 right now, hopefully it works and if it does I will update to 4.1.11.1
Thanks guys, first post so don't be too rough...
Click to expand...
Click to collapse
???
I've wiped so many times i can't even remember. Before and after each thing i said that i did a wipe...so no go on that, but it doesn't matter anymore. i've updated to rooted Donut 1.6 now. Thanks anyways tho
First, I searched and read all relevant threads concerning this issue. The five threads that showed up in the search did not help me solve my issue.
So on to my problem. I can no longer flash any rom onto my device. I attempted to flash the first official CM10 nightly (which I recently found out was not flashing properly for others) and had no success. I simply got a black screen and nothing more. I eventually got back into TWRP (v2.2.1.4) to try and Nandroid restore, but I noticed that /data was not formatting and the restore failed. Every time I would slide the bar across to confirm the restore TWRP would reboot itself. I then flashed CWM (v6.0.1.0) and the same problems were there. After that I flashed an earlier version of TWRP and successfully restored the backup. I'm not 100% sure how it was successful. So I decided to try flashing another ROM and no go. Same problems. Anyone have any ideas? When I was using CWM I got the error message below.
Code:
E: unable to locate volume information
E: unable to open ums lunfile '/sys/devices/platform/usb_mass_storage/lun0/file'
E: unable to format data
I'm running Bugless Beast with Motley #219
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
aznxk3vi17 said:
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What rom did you attempt to flash?
elementur said:
What rom did you attempt to flash?
Click to expand...
Click to collapse
So do I.I attempted to flash the first official CM10 8.18 nightly and had no success. I just got a black screen.Even more I boot into bootloader and choose to boot into recover but just stay at google logo.I try to flash recover once more,but just can't boot into recover!!
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Shano56 said:
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Click to expand...
Click to collapse
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
phiracle said:
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
Click to expand...
Click to collapse
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
android1234567 said:
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
Click to expand...
Click to collapse
Thank You Very Much!!!
I am having much the same problem as the OP. I finally rooted my Nexus 7 using WugFresh's Nexus Root Toolkit. It seemed all went well. I chose to use TWRP in a first attempt to install a ROM (I was on rooted stock), and following the instructions for installing my chosen ROM I went into it to wipe cache, Dalvic Cache and data. Both cache and dalvic cache wiped without issue, but when I attempted to wipe /data TWRP simply reported that it failed. With that failing, I did not attempt to install a rom. I was still able to boot out of recovery, but even with repeated attempts wiping data always failed. Is any one aware of any solution or have any suggestions. Thank you!
Hi. First post so apologies if I get anything wrong. Please let me know and I'll happily correct.
Picked up a SM-N9005 and successfully flashed CWM and rooted using heimdall. I then ran into two problems.
First I tried to Encrypt the device - (I need this for my ActiveSync device permissions to work so I can get office emails) and the device wouldn't encrypt. It starts the process (asks for a password confirmation only, not a new password), and then powers off and on back to brightly colored password screen.
So, I thought it might be the rooting process that had caused the issue. so I did a cwm backup and a factory reset. (foolishly ignoring the the message on the rooting thread OP). The phone still didn't encrypt so I decided to download the stock rom and revert to the old recovery.img. The plan was to go to the stock recovery, encrypt and then reflash cwm.
While waiting for the stock rom to download I (still foolishly) decided to restore all my apps and data since it clearly wasn't the problem. and... bootloop.
So my questions are :
1) Is there any way to fix the bootloop without reflashing the whole stock rom?
2) How do I encrypt the phone? Is this a clockworkmod issue?
3) How do I backup the phone - would a Titanium backup zip work or am I just going to put my phone into a loop again?
Thanks
-------------------
Further edit. I had a pit I pulled down when I first got the phone (I've bricked them before). Adding to @Nani's response below. I've tried flashing the stock rom and I get a PIT upload failure. It doesn't recognize the PIT and hiemdall can't detect a PIT on the device.
tahnoonp said:
Hi. First post so apologies if I get anything wrong. Please let me know and I'll happily correct.
Picked up a SM-N9005 and successfully flashed CWM and rooted using heimdall. I then ran into two problems.
First I tried to Encrypt the device - (I need this for my ActiveSync device permissions to work so I can get office emails) and the device wouldn't encrypt. It starts the process (asks for a password confirmation only, not a new password), and then powers off and on back to brightly colored password screen.
So, I thought it might be the rooting process that had caused the issue. so I did a cwm backup and a factory reset. (foolishly ignoring the the message on the rooting thread OP). The phone still didn't encrypt so I decided to download the stock rom and revert to the old recovery.img. The plan was to go to the stock recovery, encrypt and then reflash cwm.
While waiting for the stock rom to download I (still foolishly) decided to restore all my apps and data since it clearly wasn't the problem. and... bootloop.
So my questions are :
1) Is there any way to fix the bootloop without reflashing the whole stock rom?
2) How do I encrypt the phone? Is this a clockworkmod issue?
3) How do I backup the phone - would a Titanium backup zip work or am I just going to put my phone into a loop again?
Thanks
Click to expand...
Click to collapse
We are now a few to have encounter this bootloop issue.
At this time there's no good way ... I had to hard reboot a few times and the only workaround i found is that boot loop occurs only when phone is on (meaning there's no boot loop in "Plane Mode"). So i hope a fix/patch will be provided soon by Samsung thru a new firmware. By the meantime i try not to reboot when "Plane Mode" is off.
What i do know is I tried a lot of configurations with no result :
- reboot with SD card removed => bootloop
- reboot with SD card removed and in "Secured Mode" => bootloop
Hi folks,
I recently rooted by N4. It was running Android 5.0.
I also have MultiROM installed, with CyanogenMod installed as a secondary ROM.
I didn't realise I couldn't apply the OTA updates to the stock Android system (my oversight), and I allowed the device to download and (attempt an) the recent 5.0.1 update from Google.
When the update attempted to reboot the device, I could see in the terminal data that popped up, that it failed.
After that device now gets stuck in the booting stage with the little coloured balls drifting around.
I continued to use my phone with the secondary ROM (Cyanogen) for some days until I had time to sort this out.
MY ATTEMPTED RECOVERY
I read that ordinarily on a rooted device one would manually apply the various image files from the full 5.0.1 package.
So, following instructions found here: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Using method two (long method).
... In fastboot mode I flashed the system, boot, recovery, cache (after clearing cache), radio images from the 5.0.1 stock image.
At first I didn't flash the bootloader (as I wanted to maintain the multiboot loader I had installed) nor the user.img (I don't want to lose my user data). I read this should work. But it didn't.
When it came to booting into recovery mode to finish the process, an android icon with a ! warning on it would appear, and I could not do the recovery.
So, I have since flashed the bootloader also. That didn't change much, except that my dual-boot boot loader is now gone, and the device is still not recoverable.
Is there something I am not doing correctly? How can I recover this device so that it has 5.0.1, my existing user data, and my existing dual boot bootloader?
Cheers,...
May have solved it...
I'll post another update in a moment. Posting this just in case someone starts responding to my question in the interim.
After further fiddling around, I may have resolved this issue. I've managed to get it into recovery menu, rebooted from there, and device is now in "Android is updating" mode. Looking good.
Will post new message soon as to whether this was successful or not.
Issues continue
So, after the device booted a screen appeared for a fraction of a second, that appeared to be the screen for selecting system language (as per what happens when a device is first run after a clean install). But the screen almost instantly goes black except for the little network icon and battery icon and time in the top right of the screen.
If I use the power button to lock the screen and again to activate it, the screen very briefly flashed up the language selector, then goes blank again.
So... it seems something odd is happening after applying the 5.0.1 file.
Any suggestions?
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
AndroidWelcome said:
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
Click to expand...
Click to collapse
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Bootloop no more...
ariesgodofwar said:
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Click to expand...
Click to collapse
(wiping the sweat from his brow...)
After many tedious hours of messing around with this beast... there is life beyond the bootloop.
Back to a stock install.
So, now I am wondering why the SuperSu/Root process didn't work on my last round on this.
The SuperSu installer would kick in EVERY time I went into Recovery mode, and would then reboot the phone. This made it impossible to do things with ADP because I essentially couldn't get into recovery mode. I wanted to push through some of the stuff I pulled using ADP before I wiped the phone previously.
I installed MultiROM (which includes TWRP [is that what it's called] recovery system. BUT then go stuck in a Recovery loop.
Not wishing to repeat that fiasco... does anyone more knowledgeable than I (not a difficult status to achieve) have any suggestions to what might have caused those issues?
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
This http://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132 :good:
One possible solution is to flash the appropriate stock rom via odin. After booting, install twrp and root your phone. After this you can restore your previously saved stock rom via twrp.
MrDhark32 said:
Hi All,
Just wondering what's going on with my phone - it's a Galaxy Note 4 SM-N910G with Optus Australia.
Here's the situation:
I rooted my phone using Chainfire method from 5.1.1 Optus firmware.
Then, I installed TWRP, backed up all partitions (INCLUDING EFS).
After that, installed Cyanogenmod. Holy damn, I need to go back to stock...
so...
I booted back into TWRP
I reset phone as usually would to restore/install ROM.
I restored firmware backup in TWRP.
Reboot to system
-- BOOTLOOP --
happens every time i try to restore, and the only way I can use my phone right now is to reflash Cyanogenmod 12.1 nightlies onto it - which have problems (such as I cannot reboot with CM12.1 because if I do after installing it, the phone app breaks and I cannot get past anything because of toast message "com.android.phone" has stopped..., so then only way to get it to work again is to reflash CM12.1 again - this happens about twice daily...)
-- -- PLEASE HELP!
What happens to TWRP backups that mean i cannot restore my stock backup without it bootlooping? and why can devs not post a clean stock flashable ZIP copy of stock firmwares? Its great having all these mods, but how about something that doesn't require umpteen thousand bloody applications to reflash your phone with? Whatever happened to a simple ZIP? when I see ZIPs, devs see thanks buttons being pushed!
-- THANKS
Click to expand...
Click to collapse
Sorry no help from me but I have a similar problem. At some point mine quit booting to TWRP and I got a huge OTA update a few days ago and every time I try to boot into recovery it ends up in Stock Recovery only after going to little android saying installing updates(it fails & eventually goes to stock recovery.) I did a reset and still have 5.1.1 installed and still have the same behavior.
I have the professional version of the unified toolkit and it says if it is still booting into stock recovery select options 7, 3 which I did but it didn't fix the problem. I think what's getting me is it thinks there are still system updates to install.