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.
Related
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!
Well well. I know it may surprise you to see me here
I was messing with busybox, trying to update it. Apparently I did something wrong and the phone doesn't boot now. It'll go on the bootanimation, but at the very end, JUST before the menu softkeys lights come up, it instantly crashes and returns to the splash screen and the cycle is repeated.
Anything I can do to restore it back to an usable state, without losing the data I have on the phone? I know how to make it work again, that's really easy, but what I don't know how, is to make it work again without losing data.
I mean, busybox update seemed safe enough >_> Then it broke everything else.
Oh well, any answers would be appreciated.
Just a thought, no expert here but I've made changes to my phone tht caused me to get stuck and I've gone into recovery-restore-advanced restore and just restored the system part and its gotten me back to a running state.
I'm also thinking if you make a nandroid of your current state then try and fix the issue at least you can always have tht to go back to if someone gets you a better answer.
Wish you the best of luck, I hate having to wipe too!
I was born in Darkness.....
chozyn said:
Just a thought, no expert here but I've made changes to my phone tht caused me to get stuck and I've gone into recovery-restore-advanced restore and just restored the system part and its gotten me back to a running state.
I'm also thinking if you make a nandroid of your current state then try and fix the issue at least you can always have tht to go back to if someone gets you a better answer.
Wish you the best of luck, I hate having to wipe too!
I was born in Darkness.....
Click to expand...
Click to collapse
Didn't work, but it was a good idea actually. I didn't have a recent backup. Didn't make one, as I thought busybox would be easy enough and wouldn't affect much. Oops.
Man, I'm having such bad luck today... First, I accidentally deleted few gigs of stuff off my computer. Then my phone gets messed up due to something I did in busybox. Gee, what's next?
Damn....going out on a limb here but what if you back up your rom in its current not booting state. Then wipe and do a fresh install of the same Rom-backup the fresh install.
Afterwards flash the not booting backup you made and then do the advanced restore using the system IMG from the fresh install to see if it will boot?
Sorry thinking in layman's terms here.
I was born in Darkness.....
Flash the Rom over your brick it should boot back up. Busy box writes the files in /system/xbin (If I remember) so when you reflash the Rom you're using it writes everything back to normal. Just don't do a wipe and you should be good.
Anything that was changed in /system will be reset to original.. so if you had GNow it'll have to be reinstalled. Same thing with any other files in /system.
chozyn said:
Damn....going out on a limb here but what if you back up your rom in its current not booting state. Then wipe and do a fresh install of the same Rom-backup the fresh install.
Afterwards flash the not booting backup you made and then do the advanced restore using the system IMG from the fresh install to see if it will boot?
Sorry thinking in layman's terms here.
I was born in Darkness.....
Click to expand...
Click to collapse
I actually thought of this, but for some reason, it doesn't work. It still gets hard bootloops.
Double0EK said:
Flash the Rom over your brick it should boot back up. Busy box writes the files in /system/xbin (If I remember) so when you reflash the Rom you're using it writes everything back to normal. Just don't do a wipe and you should be good.
Anything that was changed in /system will be reset to original.. so if you had GNow it'll have to be reinstalled. Same thing with any other files in /system.
Click to expand...
Click to collapse
Thought of this before I did anything, but apparently it affected the /data too (The files inside there are intact, but something there is not allowing my phone to boot), thus continuing the hard bootloops.
I'm befuddled. I will have to figure this out later. For now, I just made a backup of the non-working ROM and wiped everything and flashed a ROM on it. I'll figure out what parts of /data to transfer back later. I needed a functioning phone, so yeah
Thanks for the help. If anyone else has any other good ideas, I'll try them out.
Keylogger_0 said:
I actually thought of this, but for some reason, it doesn't work. It still gets hard bootloops.
Thought of this before I did anything, but apparently it affected the /data too (The files inside there are intact, but something there is not allowing my phone to boot), thus continuing the hard bootloops.
I'm befuddled. I will have to figure this out later. For now, I just made a backup of the non-working ROM and wiped everything and flashed a ROM on it. I'll figure out what parts of /data to transfer back later. I needed a functioning phone, so yeah
Thanks for the help. If anyone else has any other good ideas, I'll try them out.
Click to expand...
Click to collapse
What rom are you using?
Grab that rom, in a zip file preferably, modify the updater script to not write to the data partition, wipe all partitions except data, flash and reboot.
Fix permissions and wipe caches if needed.
I can't write to the internal SD card anymore after doing a factory reset / full wipe and reflash (http://forum.xda-developers.com/tmo...ent/testing-debloated-dob1-rom-t3077507/page1).
The phone was working fine, the ROM is super fast and was perfect. Of course I had to flash the update to the "stable" version, right? No offense to the OP, I am sure it is just a random android glitch on my phone. Love the ROM.
Anyway, on a Mac and on the road traveling... In terminal I get the following error:
127|[email protected]:/ # fsck_msdos /storage/emulated/0
** /storage/emulated/0 (NO WRITE)
Invalid signature in boot block: 00002|[email protected]:/ #
Any ideas how I can fix this? The phone is running just fine less the write access to /emulated/0. I have tried SD fix from the market and various adb commands as well as the same or similar commands from the android terminal emulator.
In the process I was able to reformat my internal SD by mistake and therefore have no data backup (smart, I know). I am fine with starting from a factory baseline and reinstalling everything, I just need to know how to get there (eg. do something that will ensure remove the error above).
Any help would be appreciated as I have to get everything working 100% since the phone is my lifeline on the road (I know, which is why I flashed it on the road, right?).
Mordred said:
I can't write to the internal SD card anymore after doing a factory reset / full wipe and reflash (http://forum.xda-developers.com/tmo...ent/testing-debloated-dob1-rom-t3077507/page1).
The phone was working fine, the ROM is super fast and was perfect. Of course I had to flash the update to the "stable" version, right? No offense to the OP, I am sure it is just a random android glitch on my phone. Love the ROM.
Anyway, on a Mac and on the road traveling... In terminal I get the following error:
127|[email protected]:/ # fsck_msdos /storage/emulated/0
** /storage/emulated/0 (NO WRITE)
Invalid signature in boot block: 00002|[email protected]:/ #
Any ideas how I can fix this? The phone is running just fine less the write access to /emulated/0. I have tried SD fix from the market and various adb commands as well as the same or similar commands from the android terminal emulator.
In the process I was able to reformat my internal SD by mistake and therefore have no data backup (smart, I know). I am fine with starting from a factory baseline and reinstalling everything, I just need to know how to get there (eg. do something that will ensure remove the error above).
Any help would be appreciated as I have to get everything working 100% since the phone is my lifeline on the road (I know, which is why I flashed it on the road, right?).
Click to expand...
Click to collapse
Without wiping try reflashing the rom. If you have to flash an update to the rom to get the stable version you might just try reflashing that. If that doesn't work I hate to say it but go back into recovery and do a full wipe, system, data, and cache. Then reinstall rom again. Sometimes it's just as simple as a bad flash.
@Corwinder - thanks for that. I think I have tried variations of what you describe but tonight when I get back to the hotel I will have another go at it. What I can't figure is why when I re-flash or flash a backup it seems to write just fine. The error only seems to manifest after I boot into the OS.
Altamont - that is way south in the state isn't it?
Thanks again.
Mordred said:
@Corwinder - thanks for that. I think I have tried variations of what you describe but tonight when I get back to the hotel I will have another go at it. What I can't figure is why when I re-flash or flash a backup it seems to write just fine. The error only seems to manifest after I boot into the OS.
Altamont - that is way south in the state isn't it?
Thanks again.
Click to expand...
Click to collapse
Yeah, about 10 miles or so from the Oklahoma border. When people ask I normally tell them I'm about an hour west of Joplin, Mo. Just one more thing. Not sure if this would affect it but I assume your bootloader and modem are both OB1 versions. Did you have stock Lollipop on your phone at one time in other words? If so then the answer would be yes. I'm no developer but I see a lot of times when you need to have either the bootloader or the modem on the latest stock version.
Corwinder said:
Yeah, about 10 miles or so from the Oklahoma border. When people ask I normally tell them I'm about an hour west of Joplin, Mo. Just one more thing. Not sure if this would affect it but I assume your bootloader and modem are both OB1 versions. Did you have stock Lollipop on your phone at one time in other words? If so then the answer would be yes. I'm no developer but I see a lot of times when you need to have either the bootloader or the modem on the latest stock version.
Click to expand...
Click to collapse
I came from stock, yes, but I don't remember if I had to flash a new BL and modem to get to root (I was reflashing my wife's mega at about the same time). For arguments sake, say I am still stock (BL, modem)... what is your answer of yes to?
What is the logical next step?
Thanks again.
Mordred said:
I came from stock, yes, but I don't remember if I had to flash a new BL and modem to get to root (I was reflashing my wife's mega at about the same time). For arguments sake, say I am still stock (BL, modem)... what is your answer of yes to?
What is the logical next step?
Thanks again.
Click to expand...
Click to collapse
Was stock 4.4.2 or was it 5.0 Lollipop. The S5 does not come with Lollipop preinstalled or at least they weren't. The bootloader and modem you'd need would be in the stock Lollipop. So to be safe if you don't know if you were on stock Lollipop or KitKat then I would go here http://www.sammobile.com/firmwares/database/SM-G900T/ and download the version 5 listed. You would need to use Oden to flash that and then root. Then you could install your recovery and flash the rom.
Corwinder said:
Was stock 4.4.2 or was it 5.0 Lollipop. The S5 does not come with Lollipop preinstalled or at least they weren't. The bootloader and modem you'd need would be in the stock Lollipop. So to be safe if you don't know if you were on stock Lollipop or KitKat then I would go here http://www.sammobile.com/firmwares/database/SM-G900T/ and download the version 5 listed. You would need to use Oden to flash that and then root. Then you could install your recovery and flash the rom.
Click to expand...
Click to collapse
Thanks. 5.0 was pre-installed. Just bought it last month. It will have to wait for a few weeks until I get home (only travel with a Mac) unless you know a way to run odin on Mac.
Mordred said:
Thanks. 5.0 was pre-installed. Just bought it last month. It will have to wait for a few weeks until I get home (only travel with a Mac) unless you know a way to run odin on Mac.
Click to expand...
Click to collapse
Well since 5.0 was preinstalled you shouldn't need to restore a stock copy. But if you ever wanted to you can get Odin for a Mac here http://mac.softpedia.com/get/Developer-Tools/ODIN.shtml
Since it was preinstalled you have the current bootloader and modem. Just go into Recovery and do a full wipe. Not a factory reset. Wipe System, Data, cache, and Dalvik cache. After this you can reinstall that rom.
Re-occurance... NOT SOLVED
Corwinder said:
Well since 5.0 was preinstalled you shouldn't need to restore a stock copy. But if you ever wanted to you can get Odin for a Mac here http://mac.softpedia.com/get/Developer-Tools/ODIN.shtml
Since it was preinstalled you have the current bootloader and modem. Just go into Recovery and do a full wipe. Not a factory reset. Wipe System, Data, cache, and Dalvik cache. After this you can reinstall that rom.
Click to expand...
Click to collapse
Just wanted to say thanks for the responses. Back up and running and going through the fun task of reconfiguring everything. I did a clean wipe, all partitions, etc then flashed once and flashed again (first did not seem to take - hung at boot screen with notification light pulsing).
OK, back to square one. This time I figured I would "fix" the partition and managed to damage/change/corrupt the EFS partition. Now I am stuck with a fully functioning phone that nags about being in factory mode on every boot. Went to the efs folder and it did not have the two files to change, so I created them, still the same thing.
Thoughts? Should I flash back to stock and take it in for warranty?
Still on the road so anmy immediate help woould be appreciated.
Hey All,
I've upgraded my 925F to Official MM 6.0.1. Rooted it through kernel Xspace and then installed recovery TWRP_3.0_MM_S6_by_ManhIT
My only concern is when I'm in TWRP I can't reboot, it just freezes.
I can nandroid backup no problem just the reboot part freezes TWRP.
Anyone else had this problem? is there another TWRP to be used?
nb : I tried clearing cache + dalvik, freezes still happen before rebooting.
thanks for ur help.
kaemon said:
Hey All,
I've upgraded my 925F to Official MM 6.0.1. Rooted it through kernel Xspace and then installed recovery TWRP_3.0_MM_S6_by_ManhIT
My only concern is when I'm in TWRP I can't reboot, it just freezes.
I can nandroid backup no problem just the reboot part freezes TWRP.
Anyone else had this problem? is there another TWRP to be used?
nb : I tried clearing cache + dalvik, freezes still happen before rebooting.
thanks for ur help.
Click to expand...
Click to collapse
Try this TWRP form arter... this is the only TWRP being use by many of us here.. you flash it through odin or recovery...
I had the same problem and i solved changing my kernel
Inviato dal mio SM-G925F utilizzando Tapatalk
fabiok81 said:
I had the same problem and i solved changing my kernel
Inviato dal mio SM-G925F utilizzando Tapatalk
Click to expand...
Click to collapse
The issue is not the kernel... its the recovery that doesn't work when reboot to system is touch and is freezing..
Go to advance then terminal
Write reboot
Easy!
Yes i know the iusse is about the recovery but it seems because there is not compatibility between some recovery and some kernel. I tried various recovery 3.0 and i have always a kind of freeze. The TWRP... by Manhit for example gave me freeze with xspace kernel but not with hacker kernel. I don't no the reason....
Inviato dal mio SM-G925F utilizzando Tapatalk
same but different
Hi All,
I'm experiencing a freeze in TWRP after about a few seconds, the whole recovery stands still and this happens every time.
I flashed the Xspace kernel which hasn't help.
The TWRP from arter97 works great, except it doesn't allow me to copy files to my PC using MTP, message says unexpected error.
yet, the ManhIT and Original TWRP allow me to copy data but both of them freeze up after a few seconds which causing the copying to fail.
Reasons I'm doing this is because my SM-G925F start looping and I've tried flashing stock so many times to no avail.
I'm sure all i need to do is data/ factory wipe and my phone will boot fine, I just really need some data before I do that.
Is there perhaps a different kernel I can try?
or if anyone has any suggestions that would be very much appreciated.
Regards
wahwahward said:
Hi All,
I'm experiencing a freeze in TWRP after about a few seconds, the whole recovery stands still and this happens every time.
I flashed the Xspace kernel which hasn't help.
The TWRP from arter97 works great, except it doesn't allow me to copy files to my PC using MTP, message says unexpected error.
yet, the ManhIT and Original TWRP allow me to copy data but both of them freeze up after a few seconds which causing the copying to fail.
Reasons I'm doing this is because my SM-G925F start looping and I've tried flashing stock so many times to no avail.
I'm sure all i need to do is data/ factory wipe and my phone will boot fine, I just really need some data before I do that.
Is there perhaps a different kernel I can try?
or if anyone has any suggestions that would be very much appreciated.
Regards
Click to expand...
Click to collapse
Try with hacker kernel. Wipe cache but not data
callumbr1 said:
Try with hacker kernel. Wipe cache but not data
Click to expand...
Click to collapse
Thanks for your response callumbr1.
I've attempted two different kernels:
g925-hacker-echoe-kernel-V14.zip
hacker-kernel-S6-Universal-V12.zip
Above mentioned problems persist.
Since arter97 TWRP is not freezing on me, if I run a back up on the Data only. Then perform the wipe, the backup should still be there, correct?
and lets say I flash the stock ROM again if necessary and I'm able to boot the device.
Would it be possible to restore that data back up at all ?
or perhaps copy that back up to my PC and access/extract the files with a separate application?
Many Thanks
wahwahward said:
Thanks for your response callumbr1.
I've attempted two different kernels:
g925-hacker-echoe-kernel-V14.zip
hacker-kernel-S6-Universal-V12.zip
Above mentioned problems persist.
Since arter97 TWRP is not freezing on me, if I run a back up on the Data only. Then perform the wipe, the backup should still be there, correct?
and lets say I flash the stock ROM again if necessary and I'm able to boot the device.
Would it be possible to restore that data back up at all ?
or perhaps copy that back up to my PC and access/extract the files with a separate application?
Many Thanks
Click to expand...
Click to collapse
I think best thing to do is get an otg storage adapter that plugs direct to phone. They are cheap.
Then run the backup of data and store on otg storage. Then you have it safe and it can be restored at a later time with restore option in twrp.
Or you can always do a full nandroid backup.
Can you get onto the phone now? Does it boot up?
Is there anything specific you need off the phone? To be backed up?
callumbr1 said:
I think best thing to do is get an otg storage adapter that plugs direct to phone. They are cheap.
Then run the backup of data and store on otg storage. Then you have it safe and it can be restored at a later time with restore option in twrp.
Or you can always do a full nandroid backup.
Can you get onto the phone now? Does it boot up?
Is there anything specific you need off the phone? To be backed up?
Click to expand...
Click to collapse
I plan on getting one of those, they seem extremely useful. A colleague has one which I plan to use tomorrow if they remember to bring it, I will then do as you suggest.
Never done a full nandroid back up before but will do some searching on that.
Phone still hangs at the Samsung splash screen.
And its really only pictures and some videos that I want, contacts would be nice too.
PS, this happened when I plugged my device into the PC to charge it was at about 5%, and I was making use of side sync to control the device when it just shutdown. I thought maybe the battery died so left it to charge a bit, it eventually tried to boot up by itself and its been looping ever since. Was really strange cause it gave me no issues prior to this. When I tried to get to the recovery it would hang at the "installing updates" section once I flashed the stock ROM I was able to get to recovery to wipe the cache but no luck.
Thanks for your suggestions much appreciated.
wahwahward said:
I plan on getting one of those, they seem extremely useful. A colleague has one which I plan to use tomorrow if they remember to bring it, I will then do as you suggest.
Never done a full nandroid back up before but will do some searching on that.
Phone still hangs at the Samsung splash screen.
And its really only pictures and some videos that I want, contacts would be nice too.
PS, this happened when I plugged my device into the PC to charge it was at about 5%, and I was making use of side sync to control the device when it just shutdown. I thought maybe the battery died so left it to charge a bit, it eventually tried to boot up by itself and its been looping ever since. Was really strange cause it gave me no issues prior to this. When I tried to get to the recovery it would hang at the "installing updates" section once I flashed the stock ROM I was able to get to recovery to wipe the cache but no luck.
Thanks for your suggestions much appreciated.
Click to expand...
Click to collapse
They are really useful, one of the best things ive ever bought regarding my phone. I use it daily now.
As for nandroid backup, it basically backs up absolutely everything including the firmware and data and all partitions. I always do it before flashing or modifying anything. Then if anything goes wrong, you just flash back your nandroid backup.
Can i ask before this happened did you use google photos? If so and sync was on they will all be saved. If you dont use it i reccomend you to use it from now on incase this ever happens in future.
See how you go making the backup when you can then if you need help regarding flashing the stock and getting the phone working ill help
callumbr1 said:
They are really useful, one of the best things ive ever bought regarding my phone. I use it daily now.
As for nandroid backup, it basically backs up absolutely everything including the firmware and data and all partitions. I always do it before flashing or modifying anything. Then if anything goes wrong, you just flash back your nandroid backup.
Can i ask before this happened did you use google photos? If so and sync was on they will all be saved. If you dont use it i reccomend you to use it from now on incase this ever happens in future.
See how you go making the backup when you can then if you need help regarding flashing the stock and getting the phone working ill help
Click to expand...
Click to collapse
Good day callumbr1
I never made use of google photos, not the biggest fan of cloud storage to be completely honest but I do see its benefits when it comes to times like these. lol
as for the device, last night I flashed a custom recovery (arter97) and made use of the SkipSoft Android ToolKit to pull my photos, videos and documents through the adb protocol. That being said, I have the data I wanted so all is well there.
However, after wiping the cache and doing a data / factory reset. I reflashed the stock ROM, it all goes swell until the android pops up with a message displaying " installing system updates". It gets to 32% changes to erasing then restarts , and this happens constantly no matter how many times I flash it or restart the device.
I read on another forum that my devices is probably dead and it could be the mother board. Any thoughts?
You think maybe a custom ROM would bring it up?
wahwahward said:
Good day callumbr1
I never made use of google photos, not the biggest fan of cloud storage to be completely honest but I do see its benefits when it comes to times like these. lol
as for the device, last night I flashed a custom recovery (arter97) and made use of the SkipSoft Android ToolKit to pull my photos, videos and documents through the adb protocol. That being said, I have the data I wanted so all is well there.
However, after wiping the cache and doing a data / factory reset. I reflashed the stock ROM, it all goes swell until the android pops up with a message displaying " installing system updates". It gets to 32% changes to erasing then restarts , and this happens constantly no matter how many times I flash it or restart the device.
I read on another forum that my devices is probably dead and it could be the mother board. Any thoughts?
You think maybe a custom ROM would bring it up?
Click to expand...
Click to collapse
Thats good about your data :good:
As for the little android guy and the installing updates then erasing, this normally happens. It happens every single time i restore and normally boots fine just after its not normally an issue. After yours says erasing does it then just reboot and restart the process of erasing constantly?
What i would suggest first is to flash a different stock ROM, preferably one with newest bootloader.
After flashing, boot to recovery and wipe dalvik cache. If it gets as far as the samsung logo just leave it as the first boot can take a while... like 30 minutes.
If that doesnt work try to flash a custom ROM. I reccomend CarHD ROM. I uave used it for quite some time and no issues.
It deffinately does not sound like motherboard issue. Normally you would have many issues and errors on boot prior to having main board issues.
See how you get on and keep me updated.
callumbr1 said:
Thats good about your data :good:
As for the little android guy and the installing updates then erasing, this normally happens. It happens every single time i restore and normally boots fine just after its not normally an issue. After yours says erasing does it then just reboot and restart the process of erasing constantly?
What i would suggest first is to flash a different stock ROM, preferably one with newest bootloader.
After flashing, boot to recovery and wipe dalvik cache. If it gets as far as the samsung logo just leave it as the first boot can take a while... like 30 minutes.
If that doesnt work try to flash a custom ROM. I reccomend CarHD ROM. I uave used it for quite some time and no issues.
It deffinately does not sound like motherboard issue. Normally you would have many issues and errors on boot prior to having main board issues.
See how you get on and keep me updated.
Click to expand...
Click to collapse
It doesn't say erasing after the first time. Right after the flash it will reboot to the blue screen with the android, it displays Installing update with a percentage bar which gets to 32% then that disappears and shows erasing, then again it shows installing update with no percentage bar. The android guy has a two arrows on his chest spinning which eventually stops. The device then reboots. It goes back to the Android guy but this time it shows "installing system update" without the percentage bar, it will then freeze again then reboot. That will continue forever until the battery dies.
After flashing though I can't seem to get to recovery to wipe the cache, I hit the buttons as I always do, but the blue screen and android always appears.
This is the stock ROM I'm currently using:
https://www.sammobile.com/firmwares/download/105085/G925FXXU4DPJB_G925FXFV4DPJ2_XFV/
Do you perhaps have a link to that custom ROM? would it work fine with the service provider here in SA (Vodacom) ?
And well at least that is some good news, I'm not too keen on having to take this into a shop and pay for parts.
wahwahward said:
It doesn't say erasing after the first time. Right after the flash it will reboot to the blue screen with the android, it displays Installing update with a percentage bar which gets to 32% then that disappears and shows erasing, then again it shows installing update with no percentage bar. The android guy has a two arrows on his chest spinning which eventually stops. The device then reboots. It goes back to the Android guy but this time it shows "installing system update" without the percentage bar, it will then freeze again then reboot. That will continue forever until the battery dies.
After flashing though I can't seem to get to recovery to wipe the cache, I hit the buttons as I always do, but the blue screen and android always appears.
This is the stock ROM I'm currently using:
https://www.sammobile.com/firmwares/download/105085/G925FXXU4DPJB_G925FXFV4DPJ2_XFV/
Do you perhaps have a link to that custom ROM? would it work fine with the service provider here in SA (Vodacom) ?
And well at least that is some good news, I'm not too keen on having to take this into a shop and pay for parts.
Click to expand...
Click to collapse
Thats pretty much exactly what happens to mine after restoring or flashing but mine boots up.
Flash the firmware again but in odin options uncheck auto reboot. This time after flashing, the phone should stay off. Then you can boot to recovery.
If that doesnt work, whilst it is on the blue screen with android guy hold only vol down and power, phone will reboot, as soon as the screen goes off switch to recovery combo and this should force it to recovery.
https://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519/page1427
Here is the link to custom ROM, it will work fine on your phone. You need to flash this through TWRP. If you need steps on how to do this please tell me.
callumbr1 said:
Thats pretty much exactly what happens to mine after restoring or flashing but mine boots up.
Flash the firmware again but in odin options uncheck auto reboot. This time after flashing, the phone should stay off. Then you can boot to recovery.
If that doesnt work, whilst it is on the blue screen with android guy hold only vol down and power, phone will reboot, as soon as the screen goes off switch to recovery combo and this should force it to recovery.
https://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519/page1427
Here is the link to custom ROM, it will work fine on your phone. You need to flash this through TWRP. If you need steps on how to do this please tell me.
Click to expand...
Click to collapse
Man I think I'm just going to try the custom to see if it works.
Would I need to flash a custom kernel or can it be stock?
After flashing the kernel with twrp I'm going to assume I would follow the same step.
1. flash TWRP custom recovery
2. copy .zip file to sdcard
3. go to recovery, install , select the .zip
Is that it or am I missing anything else when it comes to flashing ROMs through the recovery?
wahwahward said:
Man I think I'm just going to try the custom to see if it works.
Would I need to flash a custom kernel or can it be stock?
After flashing the kernel with twrp I'm going to assume I would follow the same step.
1. flash TWRP custom recovery
2. copy .zip file to sdcard
3. go to recovery, install , select the .zip
Is that it or am I missing anything else when it comes to flashing ROMs through the recovery?
Click to expand...
Click to collapse
Thats it.
Before installing rom go to wipe in TWRP, wipe data, dalvik, cache and system.
You dont need to flash a kernel though.
However when flashing carhd rom aroma installer will go through some choices, from there you can choose to install arter kernel. I reccomend doing this rather than keeping stock kernel.
Remember once installer complete and rom is installed leave it a while if it hangs on samsung logo screen. It can take a while to boot.
callumbr1 said:
Thats it.
Before installing rom go to wipe in TWRP, wipe data, dalvik, cache and system.
You dont need to flash a kernel though.
However when flashing carhd rom aroma installer will go through some choices, from there you can choose to install arter kernel. I reccomend doing this rather than keeping stock kernel.
Remember once installer complete and rom is installed leave it a while if it hangs on samsung logo screen. It can take a while to boot.
Click to expand...
Click to collapse
Currently waiting on the custom to download, don't have the quickest internet connection.
while I've been waiting, I've tried the stock ROM again.
something I forgot to mention before, which has happened a few times:
During the blue screen with the droid stating installing updates.
it switches to a screen with a big yellow triangle two dots below it and a dead droid.
After this I get to recovery, I wiped the cache and its getting to the samsung logo but freezes and then restarts all over again.
I'm just curious if you know what the yellow triangle thing means?
wahwahward said:
Currently waiting on the custom to download, don't have the quickest internet connection.
while I've been waiting, I've tried the stock ROM again.
something I forgot to mention before, which has happened a few times:
During the blue screen with the droid stating installing updates.
it switches to a screen with a big yellow triangle two dots below it and a dead droid.
After this I get to recovery, I wiped the cache and its getting to the samsung logo but freezes and then restarts all over again.
I'm just curious if you know what the yellow triangle thing means?
Click to expand...
Click to collapse
I think it normally means a failed update. Sometimes there are instructions to use smart switch other times it just means the update failed.
Try with the custom ROM and keep me updated.
So after updating my bootloader to the new version so I can run Android Nougat however I wasn't getting any LTE connection and decided to restore the EFS backup I had from android MM.
My phone started having problem more problems (SIM card not being detected) and I decided to run the OPX recovery and switch back to default.
However this resulted in my bootloader getting locked for some reason and whenever I try to reboot my phone the screen is black and the LED indicator turns white.
I can boot into the factory OPX recovery but I'm forced to use the volume and lock buttons because I can't use my touchscreen whilst using this (no idea whether this is normal).
I can still boot into fastboot mode and have tried to sideload a new ROM however this has been to no avail.
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Hmm, okay thanks for your reply. But is it really a hardware problem? It sounds weird but maybe replacement is a way...
It strange, since I had the problem with my phone there are 3-4 new threads now in this forum were people have exactly this problem, black screen with white led.
I will not flash my phone again in the foreseeable future and just use gravitybox instead.
Mutchatcho said:
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
Click to expand...
Click to collapse
I did the exact same thing as you and ended up in this situation.
adefigo said:
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Click to expand...
Click to collapse
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Miniheadshot said:
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Click to expand...
Click to collapse
With the new mainboard and the new rom build, it is impossible to use twrp or root. I didn't know that when I wrote I would be using gravitybox from now on and not flash custom roms again.
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Mutchatcho said:
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Click to expand...
Click to collapse
What is your built number?
adefigo said:
What is your built number?
Click to expand...
Click to collapse
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Mutchatcho said:
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Click to expand...
Click to collapse
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Ah okay, I didn't know that. Obviously then I got maybe the other one.. but not sure if this makes the difference.
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
dchrono said:
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
Click to expand...
Click to collapse
No, did not change twrp versions during flashing new ROM and wipe to restore backup. Don't know if I remember correctly but I think I was on Bluesparks twrp (was it 3.0.0?) and did not change that during the processes.
i also had same problem
i try to update my twrp recovery with flashify. it was successful but now i cant boot into recovery. i dnt know bootloader is locked or not. i can use many fastboot commands like fastboot reboot-bootloader, fastboot continue. please help me. i try many times to update or remove twrp but nothing happend. rom is working.
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
I never changed twrp version during this until it was removed by MsmDownloadTool.
I also noticed that adb sideloading using OOS's old stock recovery with a OOS OTA zip doesnt work, it either gets stuck at logo or loops. Sideloading newer OTA zips kills the phone more because I tried to flash a MM zip and found that recovery no longer works. I've tried redownloading the MsmDownloadTool package and using this other modified MsmDownloadTool here a few replies down https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Another thing I noticed is that windows detects a bunch of unreadable local drives, with one readable containing only an 'images' folder, with useful-looking stuff like adsp.b00, adsp.b01 all the way to adsp.b12 and also .mbt files. I can provide the full list if it's useful. It's also detected in the device manager as "Marshall London HS-USB Diagnostics 9006 (COM6)" under Ports.
I really hope that I don't need to send this phone back to oneplus.
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
Click to expand...
Click to collapse
Exactly what I did and what happened to my phone. I had to send it back to repair and got it back with a new mainboard in a state that I cannot use twrp any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Did you try to adb sideload flash the 3.1.4 on the 14 version?
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt phone back to oneplus.
Click to expand...
Click to collapse
I had flashed a ROM and wanted to restore a backup of MOOS. The back up restored no problem but when I booted it wouldn't detect sim trays and no wifi. When I typed *#06# no iemi's and finally when I checked about phone I had no baseband. I had a back up of efs and persist but wouldnt help. If this sounds like your issue or if anyone's having this problem its actually easy fix. With adb commands had to delete modem1 and modem2 files. I had my doubts but after reboot sims trays detected, wifi and iemi's restored.