Before I flashed Lineage 16 in my tab, I made a backup in twrp. I didn't do it correctly and it failed. Lesson learned. I have made one in my S5 that works perfectly.
I would like to have the stock rom backup if I ever need it. Lenovo gave me the Open Source Code which is a .tar.bz2 and the Lenovo MOTO Smart Assistant to install it with.
In the tool under rescue, the only Yoga Tab 3 Plus says it's "Only for Korea" (attached pic) and the Lenovo rep said the tab "might've been set to Korea (region and language). Under language in
Lineage it says English United States.
Will I have problems if I install the tar over Lineage?
Related
While experimenting with the various ROMs available, I concluded that currently, I needed the stock firmware on my Galaxy Tab 4. After searching for hours to no avail, I finally came to the realization, that I already had the firmware on my girlfriend's untouched Tab 4! Yea... I bought 2. All I had to do was install TWRP 3.0 into her tablet, do a Nandroid Backup of her System and then transfer the backup to my tablet to restore it. It worked flawlessly.
I would like to make the Nandroid Backup available to others, but haven't figured out how to share files in these forums.
EDIT: Sorry about the title error. The Stock version is 5.0.2
LasVegas
Hi ! @Nick Verse
I know you are done with CM12.1 for this device, I just wanted to ask one thing about this ROM.
So my GALAXY J5 ( J500H/Dual-Sim ) recently had it's Warranty expired. I urgently went and Flashed this CyanogenMOD ROM for this device.( I've already done same things years ago for my GALAXY Ace )
What I did was ;
*from official 5.1.1 firmware, I installed your recommended Recovery. ( the TWRP from the link )
*Rooted it.
*Did a nandroid backup. ( clean/full system/stockrom and rooted )
*followed strictly the instructions in the first page.
*flashed the CM12.1 for J500H and ARM_5.1_gapps(mini).
*did a Dalvik/Cache wipe afterwards.
Everything seems to be working but the only thing the bugs me is that, whenever I use SimTool Kit and ask for my current prepaid balance on my service provider...
The Service provider message is always accompanied by another message that contains :
*"Invalid request format. Cannot be processed".
Any way to fix it?
Hi I am Rupesh from India and I have lenovo a3000 brought on March 2014. I want to install stock ROM on this device.
*
Up to two years I have used it nicely and after that I heard about custom ROM so I have rooted the device and installed super user app and from that time all the problems created one by one such as the device performance was very slow etc.,. Due to the above problems I have formatted the device in cwm recovery manager and after that I tried to flash custom ROMs downloaded from XDA but failed to do so many times. Four days back I have taken the device to unknown technician and he installed some aosp original ROM with twrp recovery manager but the device performance is again slow and so I have again formatted the device in twrp recovery manager and tried to flash custom ROM but failed.
*
At present I have installed lenovo downloader *and Qualcomm driver's and tried to flash in lenovo downloader but again failed. Finally I have installed latest version of lenovo moto smart assistant and connected the device in fastboot mode but the above app failed to detect the device and even I am unable to enter device name in the app. After that I have downloaded original stock ROM from lenovo forum and copied firmware folder contents to ROMs files of lenovo smart assistant which is located in program data folder of c drive after that I clicked complete button in smart assistant but there is no progress.
*
At present I don't want to install any custom ROM etc.,. Can you please suggest how to make my tab work as when I brought it I mean how to flash original stock ROM on the device.
*
Regards,
Rupesh.
What I have:
I have a Samsung J5 (2015) SM-500FN which ran out of storage and basically hung itself up. There is no data I want to recover, but I want to install either a stock ROM or (preferably) something else like Lineage - I just want to get a usable phone again.
My problem:
I have tried to download *many* stock ROM
s from reputable sources like SamMobile (for this specific phone, but trying different release dates and country codes) but every single one of those ZIPs is corrupt, even when downloading from a different computer.
Flashing with ODIN anyway gives a FAIL result and a device that cannot boot, not even into recovery: It gives a green screen with the text: `An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.`
Ironically, the Smart Switch software just says this device is not supported. The older Kies3 software lets me enter the exact model# followed by the serial# - but then it says this device is not supported. So neither Samsung software is usable, but I can still use ODIN.
Even with the phone in this broken state, I can install TWRP again. So it is not completely bricked. I boot into TWRP and copy a LineageOS ZIP file to /sdcard, but when I try to install that, the TRWP console says: `E3004: This package is for device j5nlte,j5nltexx; this device is .` Note how it doesn't appear to recognize that this device is indeed the model j5nlte!
Android.SE says that "E3004" means my TWRP is too old, but I use `twrp-3.1.1-1-j5nlte` which is currently the newest version for this phone.
I would also like to try a factory reset, but that requires the stock recovery which won't boot (see step 2 above).
My question: How do I get out of this catch-22?
It seems that if I could just get around that E3004 then I would be fine. But I have found no ways to trick the installer into ignoring that error.
Flash an updated twrp .IMG file which you can extract from the file here j5nlte (TWRP)
Just flash the img in twrp and reboot to recovery
Then with the updated twrp try flashing the rom again
garylawwd said:
Flash an updated twrp .IMG file which you can extract from the file here
Click to expand...
Click to collapse
THANK YOU! This did the trick. May I ask: what is the origin of that TRWP image? How could I have found that on my own?
torbengb said:
THANK YOU! This did the trick. May I ask: what is the origin of that TRWP image? How could I have found that on my own?
Click to expand...
Click to collapse
No problem at all, glad all is working for you now. Happens all the time with people having the wrong recovery its no big deal but a lesson learned is always make a backup in twrp before going tinckering around with things or keep a copy of a rom, that you know works, on your SD card.
From the bootleggers pie rom thread.
The Dev of that also builds his own twrp for all j5 2015 models.
he's a really great guy to have supporting our j5 community
Hi, Hoping someone can help me with my recent goofup.
I was running a version of LineageOS. Now I hadnt used the tablet for a while during the xmas break. But the last week I took out and it had rebooted on me randomly a few times. After which I decided to put a stock rom back on.
i downloaded a stock rom from sammobile and attempted to install the ROM via odin but the tablet kept rebooting me after the install process
after a few failed attempts on various ROM. I thought it might be easier to go back LineageOS so i loaded twrp back on and have been trying ever since to LineageOS 16.0
I downloded the ROM's - lineage-16.0-20200128-nightly-gts28vewifi-signed. When I try to install the ROM after following the instructions of wiping the device I get this "zip signature verification failed"
my tablet is SMT-713 so am pretty sure gts28vewifi is correct. Please can someone help me out on clues on how I get passed the hurdle.
yes such a goofup. i should have just cleared the ROM instead of attempting to put a stock rom on
Which stock ROM did you download? Was it the latest software? Fair warning, I'm a T813 owner, so I don't know anything about the T713 really, just that it's fairly similar. If you installed the wrong ROM, or the an older one, Lineage won't install. I created this guide, for the T813 about updating the firmware on it because of the firmware / install issues on LOS.