Here we go!
~no recovery ~no fastboot ~no download [rooted android 4.4]
I bought an lg wine smart 2014 (LG-D486) for nostalgia's sake. The device doesn't come with much storage space so i used a partitioned micro sd card to expand the storage.
I had it up and running perfectly with Link2sd keeping the internal storage free. One day i tried to put the system files on the sdcard through link2sd.
Again everything worked fine, a little slow but i think that was because of the partitions being a little too large.
to speed things up i thought why not try a swap partition. This is where the **** hit the fan.
I was able to reformat the sdcard to have fat32/ext2/swap partitions. The phone was running great after all the setup was finished in link2sd and swapper2.
I just finished receiving a call from a friend and the phone froze up. I removed the battery and tried to start my device back up. NOTHING. no boot logo. no vibration. nothing.
---------
when i connect it to a computer (windows) i get notification to reformat the device and two folders are readable {image/verinfo}
(with linux Reader i can see 35 android partitions)
When connected to a linux computer (ubuntu) i can see about 13 android partitions.
--------------
I've tried flashing the official .kdz file but because it won't go into download mode the updater just crashes.
I've tried unzipping the .kdz and pushing sbl1.img, aboot.img, rpm.img, tz.img, laf.img, boot.img. straight to the partitions but still no reaction.
I have another fully functional wine smart device and was wondering if there was a way to push its partitions to this device?!
all i really need is a way to get download mode working again; from there i can just factory reset the device!
i know it's a long shot but id thought id ask here before giving up.
Were you able to fix it? I've another WIne here, bootlooping....
Related
Softbricked/Bootloop
Hello,
i got some problems with my motorola phone (XT890) Razr-i, similar to Droid Razr M (expect CPU)
Yesterday i slide files (no directories) of the root partition from phone to sd-card. After that system does not run correct, thats why i made an re-boot.
Then the phone starts with the white "M" and stops. I can go to fastboot and recovery mode, no problem.
My phone is stock, i got no "root", so what can i do to put the slided files from the sd-card back to phone?
-after that all should be run like before, isn´t so?
If there is no possiblity to rescue the phone as it was, i need at least some important files from the system partition, what can i do?
Thank you for any help!!!
BR
Ron
I do also not know if i´m in the right section of forum, but the problem looks not specific to brand /vendor
btw. i got "RSD-Lite" , SDK ADB Tools on my windows pc - if i need them
Bought a quad core Onda clone tablet (AOC Leopard hardware designation) from China - yes i know, i know, it was a bad idea but the spec was so good i thought it might get me into the tablet fun everyone seems to be having - i repair em but dont really have a lot of knowledge on the software side of things for hacking these things - although after the last two weeks of hacking the thing I am becoming a bit of an expert.
Here is a link to the same one albeit with a different manufacturer made up name - as you can see the spec (Quad core, 1Gb ram, 16Gb storage and hdmi) is amazing for the price of £42 I won it for at the auction so it was more of a plaything to learn on than a big purchase for me.
I am pretty good with Linux so be as technical as you need to be.
Basically the thing buggered up when my mate plugged in the wrong power supply and thankfully it still booted albeit with the OS or bootloader I suspect corrupted.
It is stuck on the Onda loading screen leading to my assumption that it is in a boot loop.
I have spent the last two weeks trying to find drivers for windows , a compatible os and a way to get it restored - ahh the perils of buying chinese!!!
Problem I have now is that the sdcard slot is completely snafu due to my careless and fat fingered fiddling and to be honest a slight bit of temper with the thing after two weeks of head scratching - do you blame me!!!
I have managed to get it recognised by windows by trying driver after driver on the internet until i found one that worked - the perils of buying a no name chinese clone are myriad.
Without the sdcard slot the problem is now worse as i have to use the usb slot connected to the pc and sideload the apps and os but thankfully that is sorted now - Have installed the Android development Bridge - SDK toolkit and adb devices linux command was coming up with no devices but i figured it out with a lot of fiddling with the android ini file in the user profile and the dev id in system device drivers in case anyone else is trying to figure that one out - its a very obscure fix but it works.
So all is swoopy and seemed to be going well until i got the same error i was getting with the sdcard when i tried to sideload a new os - sideloads the new "update.zip" perfectly and even passes the file verification but crashes out with the fatal "unexpected error" have tried Onda official zips and Cyanogenmod flashes but i reckon the problem is because the system is not rooted and doesnt have the cyanogen bootloader installed even though i rooted it with supersu before it went up the khyber so in essence I need root to get the new os on and yes "shell su" command doesnt work as the device is only in sideload mode - only option on the 3e emergency recovery mode on the tablet is either reload from usb , sideload from usb as well as the usual clear cache, reset system and clear user data.
I should add that the hardware isnt snafu as I can see my old files and the operating system on the flash drive when i use recovery mode (power button / up volume combo) - load from sdcard option when i choose browse to sdcard - Linux always mounts the onboard flash as sdcard and an external sdcard as ext-sdcard on a tablet or smartphone - so i can select sdcard and then browse the main flash storage where i can see all my movies , development programs apk's and the Linux system itself but obviously cannot do anything else other than browse the thing for a ZIP to upload onto the \temp which is then extracted by the Emegency recovery environment - checked for verification - it then seems to prepare to install but fails with as you say the usual "unknown error" which i only assume is because I dont have root i cant go any further.
Oneclick root doesnt work.
Also tried the pad product tool v1.05 for direct flash to the tablet using Ainol Novo 10 Captain firmware and it wont even work.
Flashboot adb doesnt work.
Rockchip android tool doesnt work.
Kinda running out of ideas now!!!
Ok ok so what i need to know is basically - Does anyone know if it is possible to root and install a new bootloader from the usb sideloader - ie Adb sideload "filename".
And yes i have tried the pinhole reset button on the back of the tablet and the wipe system and reload option in the recovery menu so hopefully there are some good techies on here who know how to su the bootloader and reload the os or if it is even possible!!!
Hi everyone,
I'm trying to fix my mistake since several days but no luck.
Few days ago I rooted and updated my phone to version VIBEUI_V1.5_1423_10_ST_K910 with Gapps. Everything went fine but then while I was cleaning up the phone from useless apps I made a huge mistake by unistalling a file or apk called Idea….something(can’t remember the entire name)! I thought it was a theme file as the name was very similar to another real one. After that a neverending popup started to appear and I decide to restart the phone. Never got it back! It remains stuck on Lenovo log. I’m able to get into stock recovery where on every test or sd card format it says sdcard not found. Same when I connect it on the pc, the autorun popup only, no storage.
Seems like the sdcard is not recognized anymore so I can’t even launch an sd update.
I’m pretty new on Android systems so I’m about to give up, I don’t really know what to do anymore.
I’m beg you for some help. Any advice will be more than welcome.
Thanks
cianomanera said:
Hi everyone,
I'm trying to fix my mistake since several days but no luck.
Few days ago I rooted and updated my phone to version VIBEUI_V1.5_1423_10_ST_K910 with Gapps. Everything went fine but then while I was cleaning up the phone from useless apps I made a huge mistake by unistalling a file or apk called Idea….something(can’t remember the entire name)! I thought it was a theme file as the name was very similar to another real one. After that a neverending popup started to appear and I decide to restart the phone. Never got it back! It remains stuck on Lenovo log. I’m able to get into stock recovery where on every test or sd card format it says sdcard not found. Same when I connect it on the pc, the autorun popup only, no storage.
Seems like the sdcard is not recognized anymore so I can’t even launch an sd update.
I’m pretty new on Android systems so I’m about to give up, I don’t really know what to do anymore.
I’m beg you for some help. Any advice will be more than welcome.
Thanks
Click to expand...
Click to collapse
Hi guys, is there any way to get access into the phone root by using some tool?
I can't see the sdcard and I can't boot the phone with fastboot.
Please help.
Unfortunately I didn't get many answers but fortunately I solved the problem so I believe it would be nice to share with whom may need it:
here you have the steps I followed:
- buy a OTG cable
- Buy a USB stick 2-4GB
- Format USB stick with FAT (!)
- Put sdfuse directory on it and a K910 .qsb image inside the directory
- Plug stick via OTG in the phone
- start phone with Vol- & Power
- Choose point 4 - SD Update from the Lenovo recovery Menu
Phone will show this picture then:
Attachment 2826922
- Hit "start"
- Wait
- Be Happy
- Buy me a cigar (Partagas Series D No.4 preferred)
That's it!
Cheers
I bought this tablet thinking it would be the best of both worlds. But the partition used for Android was rather small (4GB), and got full pretty quickly. It would seem like such a hassle to resize the partition used for Windows (21gb) because they were arranged like this in disk management: 64mb-16mb-16mb-etc-1gb partition for who knows what-4gb partition for Android-more 64mb partitions-windows partition-500mb recovery partition. Now I thought I'd use my 64gb micro SD and divide it into two partitions, one being an EXT2 of 20gb for apps. I'd need to use the app LINK2SD to move the apps, but lo and behold, Android was not rooted. (I kind of assumed it was)
So I tried to root the android portion of this tablet, using information from this page
(http://forum.xda-developers.com/andr...p-cwm-t2975096), selecting T4 as the trigger. It didn't show the option to install a package and I ended up selecting "recovery" instead. It rebooted into the tablet's own recovery mode, where I didn't do anything. Prior to rebooting, I got the screen to select either OS, but Windows was gone. Now what? I also tried the Kingo program via my laptop prior to the method mentioned on the link above, but it kept getting stuck at 23% and 10%, idk if that may have done something. Anyways, now when I try to force boot to Windows (by selecting "boot to windows" after pressing the power button), but all I keep getting is this command prompt-like environment. Is my windows partition lost or something? Please help.
Anybody? Help
Before I start, I'm aware there are great data recovery guides on this forum and elsewhere. Unfortunately, I was unable to find one pertaining to Nougat and my specific circumstances. Thank you for bearing with me.
How the Data Was Wiped
I ran "fastboot format userdata" to fix a "Decryption Unsuccessful" error message after going from LineageOS 14.1 to 15 on a Xiaomi Mi 5 Pro. Because I was in a hurry to get my phone back online, I foolishly assumed the wipe would leave /data/media intact, just like TWRP, without making sure of it. I know the assumption was wishful thinking at best and I can see the irony in then spending the rest of the day trying to undo the damage.
How the Data Was Dumped
Immediately after finishing the fastboot format, I booted back into TWRP 3.1.1-0 where I discovered the extent of the data loss. Since I hadn't flashed a ROM and didn't want to write anything else to my /data partition, I did a "adb pull /dev/block/sda14 sda14.img" on my computer over USB with my phone still in recovery. With a 128GB phone, the process took a whopping 8102.059s to finish.
How I attempted to Recover Data
I let both R-Studio 8.3 and UFS File Explorer Professional Recovery 5.23.4 scan through my dump to no avail. All they found were meaningless, small files, mostly in a .txt or .so format. I also attempted to mount the image using DiskInternals Linux Reader 2.6, but PhotoRec didn't recognise the volume.
Where do I go From Here?
Christian Weiske wrote about his attempt at recovering photos from a Galaxy S5 mini, running Marshmallow. He noted that data he pulled in Windows was broken using various commands until he tried "adb exec-out". Does the problem lie in my pulled data also being broken/incomplete, or is "fastboot format" actually capable of completely destroying more than 100GB worth of data in mere seconds on TRIM-enabled devices? If I am to do a second /data dump using a different method, I would have to do it directly to my computer as my phone doesn't have a microSD slot. I should add that, to the best of my memory, I never encrypted the storage, as I went directly from CyanogenMod to LineageOS using the experimental migration build.
To anyone who chimes in, if only to tell me that I should suck it up and stick to whatever data I have backed up and move on, I'll be most appreciative! Even more so if anyone can shed some light on modern-day Android data recovery/wiping and limitations.
I'm going thru a recovery process myself. Using a few guides. First I completed a raw dump of the whole phone w/out installing any os over the phone. I'm about to check that and see if testdisk can find something via https://roubert.name/joakim/androidfilerecovery/
In the background, I have another dump going on from https://forum.xda-developers.com/ga...de-internal-memory-data-recovery-yes-t1994705 guide. Hopefully, something comes up.