Hi there,
just a short question: Is it possible to downgrade a Surface using Windows RT 8.1 to Windows RT (without the 8.1)?
I read something about a recovery USB image but this solution wasn't working for me. (Yeah, I deleted the recovery partition before...) My surface arrived with RT 8.1 so I don't have a USB containing Windows RT. Can I use another USB stick from another tablet?
BR
Screeny
You would probably need a recovery image for the Surface and not from some other similar tablet.
Not sure on this though, so don't quote me on this.
I have been trying to downgrade my Lenovo Yoga 11, but I haven't had any luck with the RT 8.0 recovery image found here:
forums_lenovo_com/t5/Idea-Windows-based-Tablets-and/Yoga-11-Windows-RT-Recovery/td-p/1220234
(replace underlines with dots to follow the link, can't post links due to being a newcomer...)
Not surprising, but it seems that we are actively being locked out from going back to RT 8.0
Most annoying thing in my opinion is that the tilt sensor doesn't work, so I would have to manually choose to rotate the screen
Most of the time its user error, hence why it was so highly recommended to check that you know how to use a recovery drive before removing the partition on the device. Several users have downgraded to 8.0 via recovery, there is nothing locking you out from doing so.
But yes. If its a first generation surface, you can get a surface RT 8.0 recovery image to downgrade. Microsoft host the US one themselves and then Trig0r on these forums have Surface RT 8.0 recoveries for all languages on his own file server (PM him).
The recovery image you use should be specific to the device. A yoga recovery would not work properly on a surface and vice versa (it will boot but drivers will be wrong).
If its a Surface 2. There never was an 8.0 image for them. You cannot downgrade it.
Workaround
SixSixSevenSeven said:
Most of the time its user error, hence why it was so highly recommended to check that you know how to use a recovery drive before removing the partition on the device. Several users have downgraded to 8.0 via recovery, there is nothing locking you out from doing so.
But yes. If its a first generation surface, you can get a surface RT 8.0 recovery image to downgrade. Microsoft host the US one themselves and then Trig0r on these forums have Surface RT 8.0 recoveries for all languages on his own file server (PM him).
The recovery image you use should be specific to the device. A yoga recovery would not work properly on a surface and vice versa (it will boot but drivers will be wrong).
If its a Surface 2. There never was an 8.0 image for them. You cannot downgrade it.
Click to expand...
Click to collapse
Got it! Recovery wasn't working for me because the stick wasn't recognized as bootable.
Now I found a workaround (maybe this is working for the Surface 2 too? Would be very nice! Could some test it, please?)
At first create a bootable recovery stick with the current Windows RT version (maybe a downloaded image will work too). Download the recovery image for Windows RT 8.0 (search for Surface RT Recovery Image (Windows RT 8.0) ) and copy the "sources\Install.wim" file to your created bootable recovery stick.
Because my english isn't so good, here a short to-do list:
Use your surface to create a recovery USB stick with Windows 8.1
Download Windows RT 8.0 recovery image from Microsoft
Copy the file "install.wim" (located under "sources" from your downloaded 8.0 recovery image to your 8.1 recovery USB stick
Boot your surface with the 8.1 recovery USB
Start a cmd session (after choosing "Troubleshoot" -> "Advanced options" ...)
Use diskpart to delete both recovery partitions and the system partition
Create a new partition and format it with NTFS
Make it active and assign this partition a drive letter (for example G
Close diskpart
Use dism to install the Windows 8.0 image to your drive (if you saved the "install.wim" from the Windows RT 8.0 image to your USB sticks root dir, use this command: dism /apply-image /imagefile:\install.wim /index:1 /applydir:G:\
After applying the image use bootrec /fixboot
Close cmd and restart your Surface
This worked for me like a charm
Greetings
Screeny
Hmm, maybe my recovery files are messed up or something.
I haven't been able to get it to boot correctly from the usb-stick (if at all).
The led flashes on the stick, and i was able to wipe the hdd (not sure if that was from a ram-disk or the stick).
I assumed that the recovery process would be able to partion the ssd but apperently not.
Now the problem is that it does not want to boot from my usb-stick, I have tried 2 different sticks with the same result:
It skips them both even though they are bootable and should have the files necessary.
TheExileFox said:
Hmm, maybe my recovery files are messed up or something.
I haven't been able to get it to boot correctly from the usb-stick (if at all).
The led flashes on the stick, and i was able to wipe the hdd (not sure if that was from a ram-disk or the stick).
I assumed that the recovery process would be able to partion the ssd but apperently not.
Now the problem is that it does not want to boot from my usb-stick, I have tried 2 different sticks with the same result:
It skips them both even though they are bootable and should have the files necessary.
Click to expand...
Click to collapse
YOu know the tablet wont automatically boot from USB unless you tell it to?
SixSixSevenSeven said:
YOu know the tablet wont automatically boot from USB unless you tell it to?
Click to expand...
Click to collapse
Yes, I have tried holding down vol+/vol- while starting it and it doesn't seem to do anything.
You turn the tablet off. Then press and hold volume down, try to power it on while still holding the button. You dont release the volume down button until the surface splash screen appears.
If that still doesn't work then you haven't created the recovery USB properly.
The other way to boot from USB (but won't alter whether it will boot from an improper recovery image of course) for Surface RT's which do boot is to swipe the charms bar in, go to settings, Change PC Settings, Update or Recovery, Recovery, Advanced Startup, Restart Now, on the choose an option screen select Use A Device which should open a troubleshoot screen where you can select advanced options and finally the name of your USB device.
SixSixSevenSeven said:
You turn the tablet off. Then press and hold volume down, try to power it on while still holding the button. You dont release the volume down button until the surface splash screen appears.
If that still doesn't work then you haven't created the recovery USB properly.
The other way to boot from USB (but won't alter whether it will boot from an improper recovery image of course) for Surface RT's which do boot is to swipe the charms bar in, go to settings, Change PC Settings, Update or Recovery, Recovery, Advanced Startup, Restart Now, on the choose an option screen select Use A Device which should open a troubleshoot screen where you can select advanced options and finally the name of your USB device.
Click to expand...
Click to collapse
Solved that yesterday, the issue was not the procedure but the tool to make the usb-sticks bootable. Thanks anyway.
I was able to downgrade my Surface RT with Windows 8.1 (it came with 8.1 pre-installed) to Windows 8.0 using someone's else recovery image and using above procedure...
everything works fine! I'm happy - I jailbreaked it and can run unsigned apps...
the only problem is I cannot activate my surface anymore... it looks like MS blocked product key which was used in recovery image...
do you have any ideas how I can fix it?
Thanks
---------------------
If anyone is interested: I activated my Surface today using telephone activation system
Screeny said:
Use your surface to create a recovery USB stick with Windows 8.1
Download Windows RT 8.0 recovery image from Microsoft
Copy the file "install.wim" (located under "sources" from your downloaded 8.0 recovery image to your 8.1 recovery USB stick
Boot your surface with the 8.1 recovery USB
Start a cmd session (after choosing "Troubleshoot" -> "Advanced options" ...)
Use diskpart to delete both recovery partitions and the system partition
Create a new partition and format it with NTFS
Make it active and assign this partition a drive letter (for example G
Close diskpart
Use dism to install the Windows 8.0 image to your drive (if you saved the "install.wim" from the Windows RT 8.0 image to your USB sticks root dir, use this command: dism /apply-image /imagefile:\install.wim /index:1 /applydir:G:\
After applying the image use bootrec /fixboot
Close cmd and restart your Surface
This worked for me like a charm
Click to expand...
Click to collapse
I haven't followed your exact steps, but I managed to install windows 8 on my Surface that shipped with 8.1 but now it's telling me it's not activated. Did you have any problems with activation?
twister2000 said:
I was able to downgrade my Surface RT with Windows 8.1 (it came with 8.1 pre-installed) to Windows 8.0 using someone's else recovery image and using above procedure...
Click to expand...
Click to collapse
Did you use Screeny's procedure? How did you activate over the phone?
Thank you both
randoof said:
Did you use Screeny's procedure? How did you activate over the phone?
Click to expand...
Click to collapse
Just after Windows 8.0 installation don't connect to network and create a local account.
Then you can go to activation and there should be an option to activate over the phone - if so - just follow the steps (when the machine will ask you on how many PCs have you installed that Windows just press 1).
Cheers
twister2000 said:
Just after Windows 8.0 installation don't connect to network and create a local account.
Then you can go to activation and there should be an option to activate over the phone - if so - just follow the steps (when the machine will ask you on how many PCs have you installed that Windows just press 1).
Cheers
Click to expand...
Click to collapse
That did the trick. Thank you.
Screeny said:
Got it! Recovery wasn't working for me because the stick wasn't recognized as bootable.
Now I found a workaround (maybe this is working for the Surface 2 too? Would be very nice! Could some test it, please?)
At first create a bootable recovery stick with the current Windows RT version (maybe a downloaded image will work too). Download the recovery image for Windows RT 8.0 (search for Surface RT Recovery Image (Windows RT 8.0) ) and copy the "sources\Install.wim" file to your created bootable recovery stick.
Because my english isn't so good, here a short to-do list:
Use your surface to create a recovery USB stick with Windows 8.1
Download Windows RT 8.0 recovery image from Microsoft
Copy the file "install.wim" (located under "sources" from your downloaded 8.0 recovery image to your 8.1 recovery USB stick
Boot your surface with the 8.1 recovery USB
Start a cmd session (after choosing "Troubleshoot" -> "Advanced options" ...)
Use diskpart to delete both recovery partitions and the system partition
Create a new partition and format it with NTFS
Make it active and assign this partition a drive letter (for example G
Close diskpart
Use dism to install the Windows 8.0 image to your drive (if you saved the "install.wim" from the Windows RT 8.0 image to your USB sticks root dir, use this command: dism /apply-image /imagefile:\install.wim /index:1 /applydir:G:\
After applying the image use bootrec /fixboot
Close cmd and restart your Surface
This worked for me like a charm
Greetings
Screeny
Click to expand...
Click to collapse
Can you please clarify this step:
[*]Use diskpart to delete both recovery partitions and the system partition*
There are 2 recovery partitions, 1 System, and 1 Primary, and 1 Reserved. You say delete the 2 recovery and 1 system, but then since the primary is there there is not enough disk space...? Can you clarify what partitions to delete and what partitions to create?
Is System=Primary???
Thanks !!
chappatti said:
Can you please clarify this step:
[*]Use diskpart to delete both recovery partitions and the system partition*
There are 2 recovery partitions, 1 System, and 1 Primary, and 1 Reserved. You say delete the 2 recovery and 1 system, but then since the primary is there there is not enough disk space...? Can you clarify what partitions to delete and what partitions to create?
Is System=Primary???
Thanks !!
Click to expand...
Click to collapse
You can just use the "clean" command for deleting all partitions on this disk.
Just select your disk "select disk X" and then "clean"
Greetings
Screeny
Screeny said:
You can just use the "clean" command for deleting all partitions on this disk.
Just select your disk "select disk X" and then "clean"
Greetings
Screeny
Click to expand...
Click to collapse
Thanks for your reply !!
But if I use clean, I cannot boot the Surface at all. It shows the "Surface" screen and then just turns off. I end up with just one partition TOTAL - just one primary; no recover or anything else and my surface will not boot.
I am using the recovery from this post.
http://forum.xda-developers.com/showpost.php?p=43597775&postcount=32
Do I need a proper MS recovery image?
EDIT: In your method, you are just recopying the primary partition, right? Install.wim just recopies to primary. How do the recovery and system partitions get recreated..
chappatti said:
Thanks for your reply !!
But if I use clean, I cannot boot the Surface at all. It shows the "Surface" screen and then just turns off. I end up with just one partition TOTAL - just one primary; no recover or anything else and my surface will not boot.
I am using the recovery from this post.
http://forum.xda-developers.com/showpost.php?p=43597775&postcount=32
Do I need a proper MS recovery image?
Click to expand...
Click to collapse
Did you used the fixboot command?
Screeny said:
Did you used the fixboot command?
Click to expand...
Click to collapse
Yes, bootrec /fixboot...
The problem is I do not have any Reserved, System or Recovery part. Only one Primary part in the end..
chappatti said:
Yes, bootrec /fixboot...
The problem is I do not have any Reserved, System or Recovery part. Only one Primary part in the end..
Click to expand...
Click to collapse
Uhm. But this should be OK ...
But you can test this by creating a new 100 mb partition and try to use the /fixboot command to this new partition.
Screeny said:
Uhm. But this should be OK ...
But you can test this by creating a new 100 mb partition and try to use the /fixboot command to this new partition.
Click to expand...
Click to collapse
Well....the way I got Windows 8.0 downgrade was to follow this thread
http://forum.xda-developers.com/showthread.php?t=2350875
I had to completely create new partitions, which was no big deal when one knows the instructions (!), and then copy images along with restoring efi boot files.
It works !
Related
This guide is for you that have a new Xoom (WiFi only, US model) with Android 3.1 and want to
- get root access
- enable the external SD card unit
Please note that Android 3.2, which now is available for the US Wifi models, make this guide more or less obsolete. If your aim is to have root access, then there are probably simpler methods.
What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and dont try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned!
I strongly recommend you to read the entire guide before trying this. In fact, read it twice to ensure that you have understood everything. If there is wierd stuff that you dont understand, dont hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but noone (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
If someone else adapts this guide for the EU model or the 3G model, feel free to drop me an IM and I will update the guide for these devices too. Until then, this has only been tested on a WiFi only, 32 GB device bought in the US. If you brick your 3G or EU bought model, dont call me ...
0. Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity)
2. Install Java SDK and Android SDK tools (for adb and fastboot commands)
3. Unlock the device for flashing (allowing replacement of recovery and boot images)
4. Install a modified recovery image (ClockWorkMod recovery for Android)
5. Root the device (Allow r/w access to the device filesystem)
6. Flash a kernel that supports the SD card (SD card access, overclocking etc.)
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows XP x86 SP3. Windows 7, Mac and Linux users will probably have to do some steps differently.
Update July 7: I have tested the procedure on Windows 7 x86 now and the procedure is identical to Windows XP.
1. Install the latest Motorola USB drivers
The installation file can be found here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2. Installation of development software
Java SDK 6 and Android SDK (for Honeycomb at least) need to be installed. You can find the installation kits here.
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
http://developer.android.com/sdk/index.html
2.1 Install them as any other software.
2.2 What I had to do was to manually modify the PATH environment variable. I use Windows XP so I did that by right clicking on My Computer, choose Properties and select Advanced. Here I added the path to platform-tools and Tools
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\QuickTime\QTSystem\;D:\Java\Android-sdk\platform-tools;D:\Java\Android-sdk\tools
Note: If the Android SDK complains that the Java Dev Kit cant be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
2.3 Test that ADB and FASTBOOT works. You should open a command window and go to your Android installation directory. Plug in your Xoom to your computer and write 'adb devices'. Your Xoom should now be listed like this
C:\Documents and Settings\Anders>adb devices
List of devices attached
0288414343813157 device
Did your device not show up? Make sure that you have USB debugging enabled in Settings / Applications / Development
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to rescure important data before you start.
3.1 Power up and start the Xoom
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'My Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal, but now ready for step 4
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
4.1 Boot into flash mode with 'adb reboot bootloader'
4.2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
4.3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.4 Enter CWM with the following procedure
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. There are ways to prevent this (see posts below), but I recommend you to redo step 4 instead of messing with removal of system files. But both methods would probably work. Experiment!
5. Rooting the Xoom
The root zip file is located here
5.1 You need to transfer the ROOT zip file to a working micro SD card. You can do this on a computer or cell phone, but the ROOT zip must be located in the root directory of the SD card.
5.2 Insert the now prepared SD card in the Xoom
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option
5.4 Select 'Install ZIP from sd card'
5.5 Select 'Choose ZIP'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install the ROM Manager app and start it. If the rooting was successful, then ROM Manager should start without any complaints.
6. Flashing a new kernel that supports SD cards (and maybe more ...)
The kernel that I used is described here http://forum.xda-developers.com/showthread.php?t=978013
The kernel zip file is located here
6.1 This step is identical to 5, but swap the ROOT zip towards the KERNEL zip. For simplicity, you may want to prepare the SD card with both zip files at the same time in step 5.1 ...
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
okantomi said:
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Click to expand...
Click to collapse
Of course, done
juDGEY2k10 said:
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
Click to expand...
Click to collapse
This is only tested on a US device. OP updated.
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
When you unlock your Xoom, it will wipe all user data.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
You're right. I rooted 1st and flashed CWR later. I then used brd's method to update to 3.1, re-root and flash the new bootloader and kernel. So there is a step missing after Step 3. I'm sorry, I don't remember exactly how to do this from HC 3.1. (meaning what files to use) as I was on HC 3.0 at the time.
BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
Yes it will. Read 3.4 again, it will do factory reset.
The root file may vary from case to case, but the procedure is the same AFAIK. I used the one that "charge light off"... There are probably others too.
bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
This is true, and I will update the OP to reflect that.
So has anyone followed this guide successfully yet? I don't really want to be the first...
yordikins said:
So has anyone followed this guide successfully yet? I don't really want to be the first...
Click to expand...
Click to collapse
Hi
I did!. And you know that someone gotta be first (actually second). Why not take the credit?
pingvinen said:
This is true, and I will update the OP to reflect that.
Click to expand...
Click to collapse
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Abracastabya said:
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
cam30era said:
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
Click to expand...
Click to collapse
Sounds good and thanks B-)
Sent from my Xoom using XDA Premium App
Tnx . Very help full .
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
rmcsc said:
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
Click to expand...
Click to collapse
Try again, and remember that timing (3 seconds) are key to success ...
I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.
I'll update in a few. Thanks!
Sent from my T-Mobile G2 using Tapatalk
Good morning everyone,
I am new to the forum, I am in urgent need of a ROM that is compatible with the device "Trio Stealth Pro 7." I installed Play Store it was working fine, but when I reset to factory defaults was locked in the boot screen. I installed a ROM then said to be compatible, the CM9, but when finished installing and I rebooted the device, the touchscreen does not work anymore.
I wish you guys give me a solution to this problem, I'm desperate and do not know what else to do!
Sincerely,
Eduardo Baptista
xduzinx said:
Good morning everyone,
I am new to the forum, I am in urgent need of a ROM that is compatible with the device "Trio Stealth Pro 7." I installed Play Store it was working fine, but when I reset to factory defaults was locked in the boot screen. I installed a ROM then said to be compatible, the CM9, but when finished installing and I rebooted the device, the touchscreen does not work anymore.
I wish you guys give me a solution to this problem, I'm desperate and do not know what else to do!
Sincerely,
Eduardo Baptista
Click to expand...
Click to collapse
Anybody can help me?
xduzinx said:
Anybody can help me?
Click to expand...
Click to collapse
This is most likely because your ROM did not come with the ft5x_ts driver that our tablet uses. I had to go through driver issues myself, but that was voluntary since I wanted a newer ROM than 4.0.4 on my tablet. If you search around the forums there are ROMs out there that will work with our tablets, the thread I have been following:
http://forum.xda-developers.com/showthread.php?t=1831257
should set you on a more correct path. Does your tablet have an HDMI port? If so, you probably have the A10 version, if not, then you probably have the A13 version. If you're interested in 4.1.1 instead of 4.0.4, then that thread should help you.
You also have the option to take it upon yourself to learn how to modify the script.bin file to include the proper touch screen interface code and make sure the proper driver is installed.
Where I am stuck right now with my modded ROM is my capacitive touch buttons don't work. You don't happen to have the ability to use lsmod and dump the results here do you? lsmod will show you what drivers your tablet is using, so you can ensure that you can see what touchscreen driver your tablet is trying to use but failing to make work.
DO THIS AT YOUR OWN RISK. YOU COULD PERMANENTLY DAMAGE YOUR DEVICE. READ ALL DIRECTIONS BEFORE ATTEMPTING.
These tablets are an LY-F1 clone. So most of the stuff that is compatible with an ly-f1 will work for you.
The model I am referring to and have personal experience with is the following: Trio Stealth Pro 7c
The Trio already comes rooted. I accidentally un-rooted mine AND I ended up with the 0.00 internal storage error. It would not let me download or install apps already on my SD card. To install a new (custom) ROM you can follow this quick guide I will put together for you.
First...
Things you will need to Download;
CWM Recovery for the Trio Stealth Pro 7c : CWM Recovery 6.0.1.2 for Allwinner A10 LY-F1/TREQ Tablets
Custom ROM for the Trio Stealth Pro 7c : Choco Ice Cream 4.0 BETA1 for Allwinner A10 LY-F1/TREQ
32 or 64 Windows ADB Drivers : Windows ADB Drivers for Trio Stealth Pro 7c
ADB needs to be downloaded and installed/setup via the Android SDK found here : Android SDK Download
1.) Download CWM Recovery
2.) After your download is finished go ahead and extract the contents to the SD card. I connected to my PC and put the extracted files (there are 3 files) on both the internal storage as well as the removable micro-SD just to be safe.
3.) Download Choco Ice Cream 4.0 BETA1
4.) After the ROM finishes downloading DO NOT extract; just copy the whole .zip file directly to the Micro-SD Card as-is.
5.) Connect your Trio to your Windows PC with a USB cable. Make sure you go to settings/Developer Options/and turn on USB Debugging. I had to open device manager and manually install the ADB Drivers. You can check to see if the drivers are installed by opening a command prompt on your computer. You would do this by going to start and typing CMD into the search bar. Or you can click on Run and type CMD into the box. This should open your command prompt. Enter each line one at a time, pressing enter after each line:
cd/
cd androidsdk/platform-tools (some of you may have to type just "tools' depending on which version you have)
adb devices
After hitting enter you should see your device's serial number. This shows that your device is connected and was found. If you do not see your device serial number either you don't have the correct drivers for your device or you did not enable usb debugging mode.
6.) Now we're going to start the adb shell by typing the following, again, pressing ENTER after each line of text.
cd\
cd androidsdk\platform-tools
adb shell
You should now see one of the following symbols:
# or $
Now type the following, again, pressing ENTER after each line of text
cd /mnt/sdcard
sh install-recovery.sh
sh reboot-recovery.sh
After pressing enter, you will see your tablet reboot into recovery mode. You can use the volume buttons to move up and down and use the power button to select. To get back into Recovery Mode if you reboot out of it or your tablet turns off; go ahead and turn your Trio completely off. Once it is shut down press the center of the volume button until the WHOLE thing is pushed in. Do this WHILE holding down the power button. Keep it held for a few seconds until you see the the screen come back on. Once you see it, you can let go and it will reboot into recovery mode.
7.) From Recovery mode:
MAKE A FULL BACK-UP FIRST. DON'T IGNORE THIS STEP!!! IT MIGHT JUST SAVE YOUR DEVICE ONE DAY!!! When the backup gets finished go back and then:
SELECT: INSTALL ZIP FROM SD CARD. (press the power button once to select it).
If you placed the ROM on the micro SD-card then you should select 'Choose zip from sd card' if you placed the ROM on your internal SD-card you should select: 'Choose zip from internal sd card'. Now find where you placed the ROM/download. Use the volume buttons to scroll up and down. Once you find it, select it with the power button. Scroll down until you see 'Install choco ice cream 4.0beta1_LYF1.zip'. Select this with the power button.
8.) It should now start to install. This will take maybe 3 minutes tops. Just be patient. When it's done, wipe the data and the cache. (it was one of the options listed when you first start recovery mode)
9.) SELECT: GO BACK; then choose REBOOT or REBOOT YOUR DEVICE or whatever and wait for the device to finish restarting. It takes several minutes to finish booting up; be patient; it will get done sooner or later.
10.) Your Finished
Here are some useful links for more Custom ROM's and other stuff you might need or find helpful:
XDA Thread for [ROM][Allwinner A10] Choco Ice Cream 4.0 BETA1 for LY-F1/TREQ
XDA Thread for CWM Recovery 6.0.1.2 for Allwinner A10 LY-F1/TREQ Tablets
XDA Thread for [rom] Unofficial CyanogenMod 9 for many AllWinner A10 tablets
XDA Thread for [rom] Unofficial AOKP for many AllWinner A10 tablets
XDA Thread for [ROM][PORT]CM9/CM10 for LY-F1/AlldroSpeed-UPDATED 13.09.2012
Good Luck...
My Galaxy Gio is broken, SUGGESTIONS WHAT TO DO PLEASE ༼ つ X_X ༽つ <<<<<<<<<<<<
Hello fellow members of this forum,
My phone was running AOKP, and today I wanted to try another ROM, so I figured I could update my CWM aswell with this nice touch edition (http://forum.xda-developers.com/showthread.php?t=2691050)
After following the instructions for the installation, I ended up with a phone who just booted - showed the samsung logo - booted again (I guess that's what you call a bootloop?)
It won't boot to recovery aswell, only Download mode
Now here comes the problem:
My Gio won't connect to Odin or Kies (usb not recognized by windows)
Things I've been trying to do:
- Boot into recovery (gets me back into the bootloop)
- Installed USB drivers and Kies (usb not recognized in download mode, however in ramdump mode Kies says it's "Connecting...", but anything wont happen) (maybe wrong USB drivers, can someone who knows they work link their drivers?)
- Tried different USB cables + ports
One thing that came up my mind is that I'm using windows 10, do you think that's the problem?
I will try previous versions of Windows tomorrow
Does anyone know how to solve this?
Thanks for reading!
Few qcom chipsets were affected by a bug in Windows 8.1 USB stack which made them not recognize in Download Mode (or fastboot mode). Drivers aren't an issue, it's the windows itself that's buggy (Actually, it's not a bug but a security feature... but is unfortunately breaking our and few other devices) here. I'm pretty much sure that windows 10 also has this issue.
Solutions:
-> Downgrade your PC to windows 8 (not 8.1) or below and Odin will work.
-> Try some dirty solutions available over the web.
And what steps did you follow to install the recovery? Flashing a recovery by the way mentioned in that thread will not make any harm to your device. Worst it can do was a 'bad recovery install' i.e. your phone won't be able to boot recovery but it will be able to boot on normal android system. Please clearly mention the steps you followed.
Bhargav97 said:
Few qcom chipsets were affected by a bug in Windows 8.1 USB stack which made them not recognize in Download Mode (or fastboot mode). Drivers aren't an issue, it's the windows itself that's buggy (Actually, it's not a bug but a security feature... but is unfortunately breaking our and few other devices) here. I'm pretty much sure that windows 10 also has this issue.
Solutions:
-> Downgrade your PC to windows 8 (not 8.1) or below and Odin will work.
-> Try some dirty solutions available over the web.
And what steps did you follow to install the recovery? Flashing a recovery by the way mentioned in that thread will not make any harm to your device. Worst it can do was a 'bad recovery install' i.e. your phone won't be able to boot recovery but it will be able to boot on normal android system. Please clearly mention the steps you followed.
Click to expand...
Click to collapse
Thanks for reply!
I'm downloading windows 8 and 7 right now to try it out, should I use the kies program to install drivers or this driver package (http://forum.xda-developers.com/showthread.php?t=961956) ?
Am I able to flash the recovery.img via Odin aswell?
Here's what I did:
- I downloaded the recovery.img and put it on the sd card
- Booted and went to terminal emulator, wrote:
su
flash_image recoveryonly /sdcard/recovery.img
- I did a reboot (not to recovery thou), and the phone became like this
Update:
Odin worked with windows 7, FINALLY GOT A PHONE AGAIN WOOHOOO :victory:
Thou I can't seem to install the touch recovery without the same happening again, but I made it work with another recovery + the rom i wanted (http://forum.xda-developers.com/showthread.php?t=2396690)
Update2:
I did some research and it turned out the recovery probably does not support RFS file system
Can I make a switch to ext somehow?
ANYWAY THANK YOU!
lemon1337 said:
Update:
Odin worked with windows 7, FINALLY GOT A PHONE AGAIN WOOHOOO :victory:
Thou I can't seem to install the touch recovery without the same happening again, but I made it work with another recovery + the rom i wanted (http://forum.xda-developers.com/showthread.php?t=2396690)
Update2:
I did some research and it turned out the recovery probably does not support RFS file system
Can I make a switch to ext somehow?
ANYWAY THANK YOU!
Click to expand...
Click to collapse
Using a CyanogenMod ROM (or ROMs based on the same) is a good option for you. They are ext4.
Frankly speaking, The steps you wrote should not break your device booting the android system. Even if it's RFS. Moreover, Recovery has no relation with android system (or its fstype).
Bhargav97 said:
Using a CyanogenMod ROM (or ROMs based on the same) is a good option for you. They are ext4.
Frankly speaking, The steps you wrote should not break your device booting the android system. Even if it's RFS. Moreover, Recovery has no relation with android system (or its fstype).
Click to expand...
Click to collapse
Yeah that's what I thought aswell, so this came as a big question mark for me, I still get the same error with the touch recovery. (nothing works when I install it).
Is it possible for you to make it flashable via .ZIP file(for use in recovery) or Odin file?
BLACK SCREEN ON BOOT ISSUE FIX
First of all Big thanks to my dear friend Ano11 for the bootloader image
If you format /sys_boot by mistake from CWM recovery and you end up with Black screen no NOKIA and only Vibrating and cant fix it on NOKIA Care Suite or NOKIA Flasher this is how to fix it.
Human Beings Issue Details:
by formatting /sys_boot you have deleted the program that will connect your phone to NOKIA Care Suite so it will no longer recognize your phone neither any NOKIA Flasher and now this is how bring it back to let the NOKIA Care recognize it again.
Alians Tech Details about issue:
formatting /sys_boot removes the bootloader which has fastboot, the device will no longer be a phone it'll be just a flash memory with alot of partitions accessible from any linux device. and since the /sys_boot is located on /dev/block/mmcblk0p3 we just need to restore a bootloader image there and it will restore fastboot that will fix everything then with NOKIA Care or NOKIA Flasher etc. "WE HAVE ADB WORKING DO ANYTHING YOU WANT!!!!!!"
Now to how to fix it!!!
Requirements:
1- Ubuntu Live CD (Dont use any other variation or another Linux because i ONLY Tested it on Ubuntu)
2- Download Attachment File.
3- A Good USB cable( i strongly recommend the original cable to avoid problems)
Steps to FIX:
1- Boot up in a Working Ubuntu (or Ubuntu Live CD)
2- Download and extract the attachment in Home Folder
3- Open up Ubuntu Menu and look up (Disks)
4- Remove your NOKIA X Battery and Unplug it from any USB or charger, re-insert battery, then hold Power button untill phone Vibrates then release power button. after you do all that plug it in USB to your computer
** if you have done those steps perfectly you should see a new device in (Disks) application will say(something-qualcomm-something) depends on the type of your phone. you will see a table on the right when you click it that has 3 partitions and then many other partitions grouped up don't touch these at all**
5- click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
7- Browse to your Home folder then in (NOKIA X RM980 BOOTLOADER) and choose mmcblk0p3.img
8- it will ask you if you are sure click Restore.
9-Wait for it to finish. when it does close Disks then unplug phone, remove battery, re-insert it, power up your phone.
BANG NOKIA APPEARS!!! The phone is back to life!!! no cloning needed and no NOKIA Care Center Needed. you can now use NOKIA Flasher and NOKIA Care Suite to restore your phone to factory firmware or use XDA Furoms to install CWM back and your favorite Custom ROM
UPDATE
You guys have asked me for the Backup procedure and i promissed to repost it but I did not have time to post so i'm very very sorry for being late!!
How to back up the bootloader partition
start up your nokia x RM-980, enable debugging, connect to USB and find an ADB then give it next comand:
Code:
adb shell
you should be in your phone shell. then:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.img
that will backup your bootloader as mmcblk0p3.img in root of your sdcard
xWaLeEdOoOx said:
Hello guys!
since we all do mistakes, i alongside alot of people have formatted /sys_boot partition on our dear RM-980.
that partition is actually the bootloader and without it the phone bricks.
the signs of that brick is black and no screen lights but a vibration that indecates "PLEASE HELP ME!!"
connecting it to windows will cause seeing a drive that windows can't detect and it will ask to format it which is the worst IDEA EVER!! and fastboot will never detect the phone.
if plugged in to Linux you'll get full control over all phone partitions including internal SD, system, boot, bootloader etc.
its easy to flash images from linux side using gparted or "disks in ubuntu which i use" but also fastboot can't be used.
all we need is an mmcblk0p3 dump to save all dead NOKIA X lives!!
it can be easily done on ADB on any computer if you are willing to help follow the following easy steps:
start up your nokia x RM-980, enable debugging, connect to USB and find an ADB then give it next comand:
Code:
adb shell
you should be in your phone shell. then:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.img
that will backup your bootloader as mmcblk0p3.img in root of your sdcard
now compress that in a zip and donate it here with your phone CODE (you can find it in the back of your phone)
I will collect the bootloaders for all the CODEs you people will send.
i don't think there will be much diffrence between them but.. we need to archive that since Microsoft is banning everything NOKIA X related out there!!
Thank you very much in advance
Click to expand...
Click to collapse
How to flash mmcblk0p3.img on linux pro? Thanks.
nguyentuyen said:
How to flash mmcblk0p3.img on linux pro? Thanks.
Click to expand...
Click to collapse
i will make it easy for you but first i need to test it. so if you have a working bootloader for RM-980 please follow my steps and upload the image on google drive, mega or mediafire and share it with us. i need to test my theory before putting people in danger.
xWaLeEdOoOx said:
i will make it easy for you but first i need to test it. so if you have a working bootloader for RM-980 please follow my steps and upload the image on google drive, mega or mediafire and share it with us. i need to test my theory before putting people in danger.
Click to expand...
Click to collapse
I use nokia X+ rm-1053,if you need i will upload it for you. Thanks
nguyentuyen said:
I use nokia X+ rm-1053,if you need i will upload it for you. Thanks
Click to expand...
Click to collapse
i'm still not sure about NOKIA X+ for where the bootloader is located in the mmc but thank you
xWaLeEdOoOx said:
I will collect the bootloaders for all the CODEs you people will send.
i don't think there will be much diffrence between them but.. we need to archive that since Microsoft is banning everything NOKIA X related out there!!
Thank you very much in advance
Click to expand...
Click to collapse
I uploaded my boot partition in this thread: http://forum.xda-developers.com/showthread.php?t=2784522&page=2
GUYS ITS NOW FIXED and i've updated the TOPIC for the instructions!!! GOOD LUCK
my nokia x is no vibrate no boot no logo no blank screen no charging now is it porsib
xWaLeEdOoOx said:
BLACK SCREEN ON BOOT ISSUE FIX
First of all Big thanks to my dear friend Ano11 for the bootloader image
If you format /sys_boot by mistake from CWM recovery and you end up with Black screen no NOKIA and only Vibrating and cant fix it on NOKIA Care Suite or NOKIA Flasher this is how to fix it.
Human Beings Issue Details:
by formatting /sys_boot you have deleted the program that will connect your phone to NOKIA Care Suite so it will no longer recognize your phone neither any NOKIA Flasher and now this is how bring it back to let the NOKIA Care recognize it again.
Alians Tech Details about issue:
formatting /sys_boot removes the bootloader which has fastboot, the device will no longer be a phone it'll be just a flash memory with alot of partitions accessible from any linux device. and since the /sys_boot is located on /dev/block/mmcblk0p3 we just need to restore a bootloader image there and it will restore fastboot that will fix everything then with NOKIA Care or NOKIA Flasher etc. "WE HAVE ADB WORKING DO ANYTHING YOU WANT!!!!!!"
Now to how to fix it!!!
Requirements:
1- Ubuntu Live CD (Dont use any other variation or another Linux because i ONLY Tested it on Ubuntu)
2- Download Attachment File.
3- A Good USB cable( i strongly recommend the original cable to avoid problems)
Steps to FIX:
1- Boot up in a Working Ubuntu (or Ubuntu Live CD)
2- Download and extract the attachment in Home Folder
3- Open up Ubuntu Menu and look up (Disks)
4- Remove your NOKIA X Battery and Unplug it from any USB or charger, re-insert battery, then hold Power button untill phone Vibrates then release power button. after you do all that plug it in USB to your computer
** if you have done those steps perfectly you should see a new device in (Disks) application will say(something-qualcomm-something) depends on the type of your phone. you will see a table on the right when you click it that has 3 partitions and then many other partitions grouped up don't touch these at all**
5- click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
7- Browse to your Home folder then in (NOKIA X RM980 BOOTLOADER) and choose mmcblk0p3.img
8- it will ask you if you are sure click Restore.
9-Wait for it to finish. when it does close Disks then unplug phone, remove battery, re-insert it, power up your phone.
BANG NOKIA APPEARS!!! The phone is back to life!!! no cloning needed and no NOKIA Care Center Needed. you can now use NOKIA Flasher and NOKIA Care Suite to restore your phone to factory firmware or use XDA Furoms to install CWM back and your favorite Custom ROM
Click to expand...
Click to collapse
my noka x rm980 059W119 v2 no power on no vibrate no boot no blank screen not detecting in pc now is it porsibal to repair
javidalana said:
my noka x rm980 059W119 v2 no power on no vibrate no boot no blank screen not detecting in pc now is it porsibal to repair
Click to expand...
Click to collapse
what did you do 1st of all?? and you need to charge your phone, keep it in charger "not pc" over night and then check if it vibrates
Please give any video of whole process because i dont see that opetion you told right click on that partion and you will see restore data from disk...
please help me to live my nxl......
Kunal111 said:
Please give any video of whole process because i dont see that opetion you told right click on that partion and you will see restore data from disk...
please help me to live my nxl......
Click to expand...
Click to collapse
In case you do not see any partitions, In that case you have not only formatted ("emptied") this partition but removed all partitions, I assume. So you have to make a new partition (or even all partitions) prior to restoring the mmcblk0p3.img disk image. I have no experience with doing this on a phone (don't know how critical the location and order of partitions is), but I guess a partition listing of a working Nokia X will help you further. Later today when I am at home I hope I can post the partition listing for you.
Help me
I have one problem how to flash that mmcblk0p3.img on nokia x
i download all file alos ubuntu .
Kunal111 said:
I have one problem how to flash that mmcblk0p3.img on nokia x
i download all file alos ubuntu .
Click to expand...
Click to collapse
It might help if you describe exactly what you are doing...
Is your device recognized as Qualcomm something at all?
In order to get it recognized on my Windows computer as Qualcomm device, I have to boot into bootloader mode, i.e.:
BootLoader Mode:
1. Turn off your device
2. Remove wires and battery
3. Hold on Volume + Key while you connect USB
4. Device should be detected as Qualcomm CDMA Technologies MSM
(copied from http://forum.xda-developers.com/showthread.php?t=2667572
So a different procedure as what the OP mentioned.
You so might try that on Ubuntu as well...
5-click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
I'hv not done only this process......
please help me how to restore
Thanxx in advanced
Kunal111 said:
5-click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
I'hv not done only this process......
please help me how to restore
Thanxx in advanced
Click to expand...
Click to collapse
Second attempt: Is your device recognized as a Qualcomm device? Do you see it in the device list on the left?
help
Yes , but how can i flast that img file on 52mb partion
Kunal111 said:
Yes , but how can i flast that img file on 52mb partion
Click to expand...
Click to collapse
And do you see the 52 MB partition on the right? What happens if you select it and rightclick on it, do you see the option "Restore partition from image" or something similar?
It helps if you post in detail what your problem is, otherwise we end up in many question-answer posts... Like we are doing now...
xWaLeEdOoOx said:
BLACK SCREEN ON BOOT ISSUE FIX
First of all Big thanks to my dear friend Ano11 for the bootloader image
If you format /sys_boot by mistake from CWM recovery and you end up with Black screen no NOKIA and only Vibrating and cant fix it on NOKIA Care Suite or NOKIA Flasher this is how to fix it.
Click to expand...
Click to collapse
Hi there,
First of all: thanks for the acknowledgements
This morning my son came to me complaining that his Nokia X was not working anymore.
I checked it and: no recovery mode, no bootloader access. Black screen, no Nokia logo, no vibration (!).
I thought: would I need this thread and my own bootloader image now?? That would be a coincidence!
Connecting the phone to the pc using USB still resulted in "Qualcomm device detected", but nothing more.
Then I noticed that the battery felt a bit loose inside the phone, also I noticed a crack in the plastic cover of the phone.
A closer look to the battery connector of the phone showed that two of them were really bent!
So I opened the casing to have a better access to the connector (really very easy using a torx T5 screw driver), nowhere these terrible plastic clips to break off when you open the device like in other phone brands...
Using my reading glasses and a magnifying glass I bent the clips back -> the phone was revived.
I guess my son must have dropped the phone real hard which resulted in bending these clips...
So people, the take home message is: also check the battery connectors closely when you experience similar problems.
Can you tell me how to back up my bootloader to an img? I have Nokia_XL.
I'm on elementary OS Freya.
ADB and fastboot are installed successfully.
vishalbiswas said:
Can you tell me how to back up my bootloader to an img? I have Nokia_XL.
I'm on elementary OS Freya.
ADB and fastboot are installed successfully.
Click to expand...
Click to collapse
Take a look at the second post, you can find the procedure in the quotes from the orginal posting of the OP (the OP removed it later from his post).
@op / @ xWaLeEdOoOx : maybe good to add this the procedure to your post again.
You may need to check if the partition name is the same for the XL version, e.g. by looking at the TWRP log files.
Hello everyone.
I still have this phone in title.
Its actual status is bricked but:
1. I am able to enter in download mode but not seen in Windows Device Manager more Linux.
2. I can enter in qhsusb_bulk mode (9006), detected in Windows and Linux but it's a tricky, unstable connection.
3. Managed to flash, using dd in Linux, the TWRP recovery but I can't access it.
4. Tried to do a factory reset - I can get to the point where it's asking if sure...but nothing happens beyond that point.
5. I have all the programs found to be used in this forum but don't have a clear image on what and how to use them.
6. I need the partitions *.img files for the 32 GB version, not the 16 gb.
7. I have the kdz and TOT files for my version. But how to I use them?
Someone can PLEASE help me?
Thanks.
BigBadSheep said:
Hello everyone.
I still have this phone in title.
Its actual status is bricked but:
1. I am able to enter in download mode but not seen in Windows Device Manager more Linux.
2. I can enter in qhsusb_bulk mode (9006), detected in Windows and Linux but it's a tricky, unstable connection.
3. Managed to flash, using dd in Linux, the TWRP recovery but I can't access it.
4. Tried to do a factory reset - I can get to the point where it's asking if sure...but nothing happens beyond that point.
5. I have all the programs found to be used in this forum but don't have a clear image on what and how to use them.
6. I need the partitions *.img files for the 32 GB version, not the 16 gb.
7. I have the kdz and TOT files for my version. But how to I use them?
Someone can PLEASE help me?
Thanks.
Click to expand...
Click to collapse
There's already a thread on it. https://forum.xda-developers.com/t/...nload-mode-after-ota-on-rooted-lg-g2.2582142/
For a stock rom, here's the link. http://storagecow.eu/?dir=Xda/LG G2/Stock
This might can help.
Absolute Territory said:
There's already a thread on it. https://forum.xda-developers.com/t/...nload-mode-after-ota-on-rooted-lg-g2.2582142/
For a stock rom, here's the link. http://storagecow.eu/?dir=Xda/LG G2/Stock
This might can help.
Click to expand...
Click to collapse
Thanks, but already did that.
I end up extracting img files from the TOT file and sending them to the phone using the dd command.
And I dd-ed every single file (36 files per total) but with no use.
Tried with TWRP recovery and with stock recovery...nada!
It must be the jumpy connection. I will try again someday later on.