Hello
I'm trying to install Resurrection Remix, but everytime the flashing is done (Rom an Gapps) the phone reboots into TWRP only. No Lenovo logo, zero, nada. I thought it was a problem with RR and tried Lineage OS just for kicks but the same thing happened.
I've done the dd if=/ command method which i used some time ago with my beloved nexus 4 and Cyanogenmod nightlies; worked like a charm back then, however this time the path doesn't seem to exist.
Glad i made a nandroid backup. My phone can be brought back as new, no loss there, but i want to try custom ROMs.
What could i possible do to fix this?
Regards
r0ckm4n said:
... the phone reboots into TWRP only. No Lenovo logo, zero, nada.
Click to expand...
Click to collapse
Do you mean you don't see the Lenovo bootlogo during boot? What do you use to make and restore the Nandroid backup? Does everything work well after restoring the Nandroid backup? Also, most importantly, what's the model name of the device you're using?
Droidge said:
Do you mean you don't see the Lenovo bootlogo during boot? What do you use to make and restore the Nandroid backup? Does everything work well after restoring the Nandroid backup? Also, most importantly, what's the model name of the device you're using?
Click to expand...
Click to collapse
The phone never gets to the Lenovo Logo, goes directly into TWRP after Reboot or Power On. Everything works after restoring from TWRP 3.0.3.
Phone model is A6020I36, Hardare Version H201.
Thank you.
r0ckm4n said:
The phone never gets to the Lenovo Logo, goes directly into TWRP after Reboot or Power On. Everything works after restoring from TWRP 3.0.3.
Click to expand...
Click to collapse
All right, time for a little bit of experimentation. Now, this could be dangerous, and I hope you know how to recover a bricked phone using QPST.
Does the Nandroid backup have a backup of the boot partition? If so, I'd like you to reproduce the issue; and when you get to the point of restoring the backup, restore everything but the boot partition. Let me know if you see the Lenovo bootlogo during the reboot sequence that follows.
Droidge said:
All right, time for a little bit of experimentation. Now, this could be dangerous, and I hope you know how to recover a bricked phone using QPST.
Does the Nandroid backup have a backup of the boot partition? If so, I'd like you to reproduce the issue; and when you get to the point of restoring the backup, restore everything but the boot partition. Let me know if you see the Lenovo bootlogo during the reboot sequence that follows.
Click to expand...
Click to collapse
I'll read everything about QPST first and then i'll proceed hopefully this weekend, i'll keep updating here.
Kind Regards
Turns out i just needed to downgrade TWRP from 3.0.3 to 3.0.2 and everything worked as it should have been from the start.
Thank you for your replies. Cheers!
Happened to me one day, Shreps TWRP it's bugged, it have two or three bugs related with F2FS and the bootloop, you always can flash the Russian TWRP for solving this
KiiKeEp said:
Happened to me one day, Shreps TWRP it's bugged, it have two or three bugs related with F2FS and the bootloop, you always can flash the Russian TWRP for solving this
Click to expand...
Click to collapse
I dont get it, can u pls explain it bro
This happened to me when I installed AOKP. Remove the battery and boot again. It works for me and that is how I do it every time there is an update. First boot takes time so don't panic.
Related
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
¿GotJazz? said:
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
Click to expand...
Click to collapse
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Ramer said:
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Click to expand...
Click to collapse
Thanks, @Ramer - I checked Sammobile earlier this morning, and it wasn't there. They must have posted it later today.
I can't get to it right now, tho, their website may be having issues. I'll try later.
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
ashyx said:
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
Click to expand...
Click to collapse
Unfortunately. @ashyx - I'm not sure exactly where now. The recovery failure was almost instant (within the first 5 to 10 steps), and I remember that the error occurred right after a progress comment about EXT4. I lost the capability to boot up, and I lost the capability to get into Recovery Mode. My only option was to stay stuck in Download Mode, and hope that my battery didn't die before I was able to get a Odin image re-installed.
It was nerve-wracking.
I wasn't sure if the tablet would be charging while in Download Mode, and there was no way (that I knew of) to get out of Download Mode. I thought there was a high probability that I was about to permanently lose my brand-new tablet.
I paid for a subscription to Sammobile to get an older image installed until someone was able to get me the more recent stock image.
I'm too nervous to try and restore the image again without need, but I will definitely do it if you want me to. I understand the urgency to make sure that TWRP makes good images 100% of the time, and I am reluctant to do anything future to my tablet if I can't make a reliable back-up.
¿GJ?
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
ashyx said:
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
Click to expand...
Click to collapse
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
¿GotJazz? said:
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
Click to expand...
Click to collapse
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
ashyx said:
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
Click to expand...
Click to collapse
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
¿GotJazz? said:
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
Click to expand...
Click to collapse
Is this backup also encrypted. I have seen that error with encrypted backups in the official twrp. However this was fixed with an update pushed to the twrp repo which I have incorporated into the latest build.
Does your version of Twrp show your model number at the top?
ashyx said:
Is this backup also encrypted?
Click to expand...
Click to collapse
Yes.
ashyx said:
Does your version of Twrp show your model number at the top?
Click to expand...
Click to collapse
No, it just shows Team Win Recovery Project v2.8.6.2. It doesn't show any Samsung model numbers (If that is what you are asking).
I installed it using your All-In-One Root/Recovery tool.
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
ashyx said:
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Click to expand...
Click to collapse
Thanks, @ashyx! I'll download the SM-T800 F2FS version right now.
BTW, I've been really interested in installing F2FS. One thing I have been worried about, though, is that once I go down the F2FS path, it may be easy to really mess things up. For example, if I update a ROM, I would always need to use a F2FS ROM, or I might lose all my data - is that right?
Normally you would only format the data and cache partition to f2fs. There isn't much point formatting system to f2fs.
Also f2fs requires a special kernel. Myself and Tkkg1994(Iron Rom) have been working together to get this working properly. Still testing.
We are almost there.
Once formatted to f2fs you would need to reformat back to ext4 and flash a kernel to return back to normal. You could then flash your backup.
[SOLVED]
Hello guys, hope that someone could help me.
I had a 4.4.2 rom (note4neo 2.0) and i wanted to try 5.1.1 so first of all i mad a full Nandroid Backup through TWRP and also a titanium bkp. Later on i installed lollipop original rom through ODIN and everything was ok. I then followed a guide from Noble Rom for rooting and installing TWRP. Everything went ok, but i had problems with some rooting app (like titanium) and so i decided to revert back to 4.4.2.
At first I rebooted into recovery, made a full wipe (even system) then restored previously backup. Seemed to be ok, but then when rebooted it stucks on boot logo (i left booting for 28 minutes, so....).
Then i tried to wipe cache, dalvik and data and reboot again: no changes.
I then decided to reflash previously twrp (the one that i used for bkp). Flashes went ok, but i have "recovery is not seandroid enforcing" message on the top (even with the lollipop twrp: maybe is this the key of my problem?!?).
Restoring backup from older twrp didn't work as well...
Of course i can enter both Download and Recovery mode.
Now i flashed back the original 5.1.1 through ODIN in order to go back to original lollipop and see what u guys can tell me to do to restore backup i made..
Thank you very much for your help
I was thinking that maybe i should flash a stock 4.4.2 before restore the backup...
Now i'm downloading it and see what happens...tell me if i may be right
Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup
lennon123 said:
Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup
Click to expand...
Click to collapse
Update: Flashed 4.4.2, all ok. Then rooted, twrp and all ok again
After i restored Backup and stuck on boot.
Then i made again all the steps: STOCK, ROOT, TWRP, then Base version of the Rom and all ok.
At this point i was thinking it was done and restoring would have been just fine...unfortunatley it doesn't. Stuck on boot again.
So i reflashed the Base version of the mod rom and: it started with my restored app Btw i'm encountering problems like no home button, no volume icon, no settings shortcut. Now i made a cache and dalvik wipe but problems still remain..
Any idea?
After some attempts to solve those problems i stucked again on boot..
So now my plan is to: Flash STOCK rom, Root, Twrp, Base mod rom (everything always ok so far) and then restore JUST DATA from backup... Not touching system and boot should let the rom works just fine...at least i hope so :'D
Ok, as i was expecting the problem is solved. I did not restored System and Boot and all apps works just fine. Even though i miss some settings i made now i'm happy to be 90% back to origin ^^
Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.
lennon123 said:
Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.
Click to expand...
Click to collapse
Yes, it's solved I'll mod the title
I was doing normal stuff when I noticed that for some reason my google account had dissapeared from the device. It is not the first time that happens not only in my N5X, but also on an old S2 so since I'm paranoid instead of just putting it again, though of some malware and decided to restore a nandroid backup I did few days ago after reflashing august v6.0.1.
I was using @jollaman999 's multirom and it's recovery, and the recovery gave some strange errors (got an screenshot but on the device..), after reboot I was stuck on Google logo, after that, the bootanimation dots appear but they dont move, and the device resets.
I tested entering bootloader then recovery, and the original TWRP 3.0.2-1 from the backup had recovered and was working, so I decided to restore the very same backup from there. Checked md5s and all good (only a warning about a ' ' or something but all the md5s were good, it asked me to disable the md5 checking option). Restored everything without a single problem, wiped caches and rebooted.. in the very same situation.
I decided to just sideload the last full OTA from August security patches, and I sideloaded it normally. After sideload, not only the problem persisted, but also the original image that appears when turning on the phone (the warning about unlocked bootloader, which usually is orange) was red and talked about corrupted phone. I just flashed TWRP with fastboot and flashed ElementalX kernel and the turn-on screen turned to be orange ok (wtf?), but nothing got fixed and I was in the very same situation.
I decided to do a complete wipe after saving the data on TWRP, including formatting system, and then sideloaded the full OTA again, again without errors, but I appear in the same Bootanimation start-bootlop status than before.
So I have access to aboot (fastboot) and can flash TWRP and use it, but something is wrong and I am kinda lost, never been on this situation. What would you do guys? The OTA supposedly flashed Bootloader, Radio, Boot, System and Vendor and checked that everything flashed OK, yet the boot animation doesn't even start moving...
The Nandroid restore image doesn't have MultiRom.
Thanks for the help guys.
---
Edit: fixed, see lower post for details.
**** the stocks
Download any rom-gapps on a USB+otg enter in to recovery wipe everything format again data then install the USB flash the ROM and will be open I suppose!
Sent from my Nexus 5X using XDA-Developers mobile app
---------- Post added at 08:51 AM ---------- Previous post was at 08:50 AM ----------
If it opens something u doing wrong with side loads
Sent from my Nexus 5X using XDA-Developers mobile app
I'm stuck with the same issue. I suspect the power button, seems like a lot of users have problems with that.
I opened my phone and took a look, but the button seems fine..
Okay, issue fixed.
The problem was the EFS partition. When I restored the backup, it included entire backup (EFS) and for some reason EFS backup on that nandroid does not work, and kills my phone..
I tested restoring everything but EFS from that backup, and then EFS from an old copy... and SUCCESS.
I didn't think EFS could literally kill the phone, but apparently it does.
Also TWRP has some nice bugs, if you restore an entire nandroid backup, it says OK including EFS (but after reboot its stuck). If you restore only EFS, it FAILS (cause /efs2 is not found or something like that.)
@Dees_Troy this happened with both TWRP 3.0.2-0 and 3.0.2-1, I had a nandroid backup where restoring everything (including EFS) gave a success but killed the phone, while trying to restore only EFS gave something like (/efs2 not found) and made the phone not boot. In a rage impulse I deleted that backup -.-, I shouldn't probably if you needed some data, but I was so damn nervous, sorry.
nokiagye said:
**** the stocks
Download any rom-gapps on a USB+otg enter in to recovery wipe everything format again data then install the USB flash the ROM and will be open I suppose!
Sent from my Nexus 5X using XDA-Developers mobile app
---------- Post added at 08:51 AM ---------- Previous post was at 08:50 AM ----------
If it opens something u doing wrong with side loads
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
Not needed, apparently it was all EFS problem, not any other partition, so either stock or custom roms were ****ed and nothing did boot. Thanks a lot for the help tho!! :good::good::good::good:
septix said:
I'm stuck with the same issue. I suspect the power button, seems like a lot of users have problems with that.
I opened my phone and took a look, but the button seems fine..
Click to expand...
Click to collapse
If it was the problem button, you couldn't be on aboot (fastboot) or recovery and do stuff .
In my case it was all TWRP+EFS problem.
RusherDude said:
If it was the problem button, you couldn't be on aboot (fastboot) or recovery and do stuff .
In my case it was all TWRP+EFS problem.
Click to expand...
Click to collapse
I thought that as well.
Well, to bad I managed to delete my backup.
septix said:
I thought that as well.
Well, to bad I managed to delete my backup.
Click to expand...
Click to collapse
If you aren't in my case (didn't try to restore also EFS.. dunno why but last time), your problem isn't probably EFS.
Anyway, don't you have an old backup of EFS? It's the first thing I do when getting a phone, boot TWRP, backup EFS, then backup the rest and save those like gold.
RusherDude said:
If you aren't in my case (didn't try to restore also EFS.. dunno why but last time), your problem isn't probably EFS.
Anyway, don't you have an old backup of EFS? It's the first thing I do when getting a phone, boot TWRP, backup EFS, then backup the rest and save those like gold.
Click to expand...
Click to collapse
I did a backup, but I deleted it by mistake. And I'm afraid I tried to flash the EFS backup at some point.
I was tired and stressed at the moment. Guess I'm buying a new phone
septix said:
I did a backup, but I deleted it by mistake. And I'm afraid I tried to flash the EFS backup at some point.
I was tired and stressed at the moment. Guess I'm buying a new phone
Click to expand...
Click to collapse
Send it to Google for repairs lol.. (it's a Nexus, a lot of people have sent it unlocked and everything and Google covers it, it's a dev device after all).
Also, thereis a thread from bitdomo in this subforum to flash the N5X with stock LG software, that fixes bootloader problems but not sure EFS, try asking him if he could solve your problem?
I have a backup of my EFS that I made with TWRP, but my bootloader is now locked and I've flashed the LG TOT. I've been trying to fix this phone for days. It's stuck bootlooping at the Google logo/4 colored dots animation.
Is there any way for me to restore my EFS partition? Or am I screwed?
How dies TWRP named an EFS Backup?
I will search for it on my hdd. Maybe I had made one.
simondo22 said:
How dies TWRP named an EFS Backup?
I will search for it on my hdd. Maybe I had made one.
Click to expand...
Click to collapse
It names it after the day and time you did the backup, but the files are named efs1.emmc.win/.md5 (at least on my mac)
Who knows, this guide is suitable for Nexus 5x?
http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
Hi everyone. My phone doesn't boot up after restoring twrp backup. Yesterday I made a Full backup and now if I try to restore that my phone just go into a bootloop. How can I resolve this problem?
mr.banana said:
Hi everyone. My phone doesn't boot up after restoring twrp backup. Yesterday I made a Full backup and now if I try to restore that my phone just go into a bootloop. How can I resolve this problem?
Click to expand...
Click to collapse
It depends on a lot of factors.
What ROM, what TWRP version, what partitions did you back up, etc.
If you want to get your phone working, you can flash any ROM of your choice from TWRP or restore stock image.
indian84 said:
It depends on a lot of factors.
What ROM, what TWRP version, what partitions did you back up, etc.
If you want to get your phone working, you can flash any ROM of your choice from TWRP or restore stock image.
Click to expand...
Click to collapse
TWRP Version is the last one (I think). I backup every partition so I made a full backup of everything. The rom Is the simple aosp. I very want back all my stuff
mr.banana said:
TWRP Version is the last one (I think). I backup every partition so I made a full backup of everything. The rom Is the simple aosp. I very want back all my stuff
Click to expand...
Click to collapse
Backing up all the partitions was the mistake.
Getting your stuff back looks difficult.
If you flash ROM using TWRP, your media files and anything stored on your phone won't be deleted.
But all your apps and stuff will be lost.
Hi at all,
with my new phone Xiaomi Mi A2 lite, I wanted doing the backup of my phone with TWRP, because in case of problem I will ready to restored it.
But I have discovery that the partition "data" is not visible because is encrypted and is impossible with TWRP to do the backup of it.
Is impossible use the storage of phone for make the backup beacuse it is also encrypted.
Is there anyone that has found a solution to decrypt and copy the partition in question?
Sorry by poor english and thanks all wonderfull team for the working doing.
If I were you, I would forget about our TWRP. It's just a half baked version which got official status by sponsorship. At best it's an early alpha version far from beeing useable.
thorin0815 said:
If I were you, I would forget about our TWRP. It's just a half baked version which got official status by sponsorship. At best it's an early alpha version far from beeing useable.
Click to expand...
Click to collapse
Thank you for the reply, I sad to reading this. So we must hope an next update for our TWRP. Now is impossible decrypted the partition entering the correct password or pattern.
So today is impossible do the full backup of app and setting....
liboriof said:
Thank you for the reply, I sad to reading this. So we must hope an next update for our TWRP. Now is impossible decrypted the partition entering the correct password or pattern.
So today is impossible do the full backup of app and setting....
Click to expand...
Click to collapse
i think you flashed the twrp image instead of booting it and then using the zip to install it. just redo the twrp installation exactly how it is written on the thread, encryption will work. restoring a backup however, does not (doesn't boot). for this you have to restore the data backup and then reflash the same rom the backup was made with from fastboot with the "flash_all_except_storage.bat". I would also recommend to do this before you try to reinstall twrp.
thorin0815 said:
If I were you, I would forget about our TWRP. It's just a half baked version which got official status by sponsorship. At best it's an early alpha version far from beeing useable.
Click to expand...
Click to collapse
Yes, it is far from usable but at least he built a working tree anyone could build a booting twrp from. it defenitely does not deserve the official status bcs this would mean it is maintained and working propperly.
wertus33333 said:
i think you flashed the twrp image instead of booting it and then using the zip to install it. just redo the twrp installation exactly how it is written on the thread, encryption will work. restoring a backup however, does not (doesn't boot). for this you have to restore the data backup and then reflash the same rom the backup was made with from fastboot with the "flash_all_except_storage.bat". I would also recommend to do this before you try to reinstall twrp.
Click to expand...
Click to collapse
Thank you for reply, I will try to do as you say and later I will write what happened.
I have used the guide by wertus33333 and it working. Thank you for your advice.