Related
Okay, before I start getting flammed for being a noob, I have rooted android phones successfully since the OGDroid, and never had any issues. I am no noob to rooting and such. But here is my problem:
I have followed the rules in this thread BY THE TEE
http://forum.xda-developers.com/showthread.php?p=20135183#post20135183
The last post in the thread doesn't give ANY links what so ever to the files he's talking about, but following the OP directions, the phone does not stay in HBoot to downgrade it, as soon as the zergs send and the phone reboots, it auto reboots again. FAST BOOT is off, Debug is on, Drivers are installed CORRECTLY, no Sync software or itunes even has ever been installed on this computer. But I run the tool as admin, including the hack-vivow.cmd and it completes, but doesn't do anything to the phone. Help?
Oh, and I will mention, no SD card. Old replacement took it with it when it fried it. So, no external SD card, but that never stopped me from rooting ANY other android phone.
Ammocache said:
Okay, before I start getting flammed for being a noob, I have rooted android phones successfully since the OGDroid, and never had any issues. I am no noob to rooting and such. But here is my problem:
I have followed the rules in this thread BY THE TEE
http://forum.xda-developers.com/showthread.php?p=20135183#post20135183
The last post in the thread doesn't give ANY links what so ever to the files he's talking about, but following the OP directions, the phone does not stay in HBoot to downgrade it, as soon as the zergs send and the phone reboots, it auto reboots again. FAST BOOT is off, Debug is on, Drivers are installed CORRECTLY, no Sync software or itunes even has ever been installed on this computer. But I run the tool as admin, including the hack-vivow.cmd and it completes, but doesn't do anything to the phone. Help?
Oh, and I will mention, no SD card. Old replacement took it with it when it fried it. So, no external SD card, but that never stopped me from rooting ANY other android phone.
Click to expand...
Click to collapse
You mention nothing of having the Android SDK Manger installed, we need more information then what you gave us. Many many people have had zero problems using this including myself multiuple times on windows 7 64bit which seems to be the biggest P.I.T.A. so hopefully I can help you get some root, cos without it, the phone suckkks. lol. Root 4 life.
I have had a dinc 2 sitting around for about 3 months and I finally decided to downgrade it yesterday. Long story short I did everything u did and followed to a TEE and no go. Then I realized I had no SD. As soon as I put one in......Viola, it worked
Sent from my Incredible 2 using XDA App
ksizzle9 said:
I have had a dinc 2 sitting around for about 3 months and I finally decided to downgrade it yesterday. Long story short I did everything u did and followed to a TEE and no go. Then I realized I had no SD. As soon as I put one in......Viola, it worked
Same here. Just got a replacement after my power button stopped working. New dinc2 had .98. As soon as I realized I took my SD card out put it back in and it worked then.
Click to expand...
Click to collapse
I do indeed concur with manwithadroid, I tried this procedure for days before realizing that I didn't have an SD card. I only realized it at that point because I tried to take a picture of my dogs playing and it wouldn't save, then.....it hit me.
OP, I would almost guarantee this would fix your problem.
Sent from my Incredible 2 using XDA App
Part of the revolutionary root process writes a file called ".17 somethingorother" to the sdcard. Seems like I've never rooted a phone without an sdcard, because alot of the processes and apps require you to place some .zip file on the root of the sdcard.
To lead off with "before anybody flames me for being a noob..." comes off pretty arrogant, and implies that you know it all anyway, so why should anybody help out?
Fwiw, I had zero issues following the same guide, and I can guarantee the links are there.
Sent from my ADR6350 using XDA App
SD card method of rooting is well known to the manufactures and that is why the newer PPCs and tablet devices are bieng "AppHoleIzed" as in Denial of User Up Gradable Storage.
That is the main reason that I will have nothing to do with the GNex.
Even the XTC clip requires the Micro SD card.
All the BS from manufactures about allowing root, just means that pay just enough attention to the forums to find ways to con us into thinking that is what they "will" do. Yea wight...
That's the main reason Willies' P Hone 7 is not doing as well as WinMo phones.
Check the forums, WinMo is doing more with an End Of Life OS then AppHole has done since the beginning.
SamSkum is going to find real soon that MOST people are NOT going to put up with a device that is locked down and so loaded with Operator Bloat that it sucks the data that now cost so much.
Root IS a vital option for people that want to actually use a device for productivity AND entertainment.
Corporate greed is going to bite them in the ass so bad they will start looking like QWest when they had to sellout the wireless just to stay afloat.
Live n learn.
I'm having the exact same problem. I followed all of the original instructions. The code runs and it claims to have rebooted but upon rebooting it still stays 2.3.4. Can someone take a look at the code from the Command Window and see what the issue is?
XDA won't let me post links since I'm a new user but I'll post the exact code here.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd \
C:\>cd Android
C:\Android>adb devices
List of devices attached
HT1BGMA10912 device
C:\Android>hack-vivow.cmd
C:\Android>if /I NOT EXIST C:\Windows\adb.exe copy tools\win\adb.exe C:\Windows
C:\Android>if /I NOT EXIST C:\Windows\AdbWinApi.dll copy tools\win\AdbWinApi.dll
C:\Windows
C:\Android>if /I NOT EXIST C:\Windows\AdbWinUsbApi.dll copy tools\win\AdbWinUsbA
pi.dll C:\Windows
C:\Android>if /I NOT EXIST C:\Windows\fastboot.exe copy tools\win\fastboot.exe C
:\Windows
C:\Android>if /I NOT EXIST C:\Windows\sleep.exe copy tools\win\sleep.exe C:\Wind
ows
C:\Android>adb shell rm -r /data/local/tmp/*
C:\Android>adb push zergRush /data/local/tmp/zergRush
1218 KB/s (21215 bytes in 0.017s)
C:\Android>adb push misc_version /data/local/tmp/misc_version
1546 KB/s (15837 bytes in 0.010s)
C:\Android>adb shell chmod 777 /data/local/tmp/zergRush
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
C:\Android>adb shell /data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Android>echo Sleeping 10 secs while adb restarts on the device....
Sleeping 10 secs while adb restarts on the device....
C:\Android>sleep 10
C:\Android>adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18
.605.3'
/data/local/tmp/sh: permission denied
C:\Android>adb reboot bootloader
C:\Android>fastboot oem rebootRUU
< waiting for device >
... OKAY [ 0.356s]
finished. total time: 0.356s
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 0.888s]
finished. total time: 0.891s
C:\Android>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra
dio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
sending 'zip' (292817 KB)... OKAY [ 52.023s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 97.349s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.159s
C:\Android>hack-vivow.cmd
C:\Android>if /I NOT EXIST C:\Windows\adb.exe copy tools\win\adb.exe C:\Windows
C:\Android>if /I NOT EXIST C:\Windows\AdbWinApi.dll copy tools\win\AdbWinApi.dll
C:\Windows
C:\Android>if /I NOT EXIST C:\Windows\AdbWinUsbApi.dll copy tools\win\AdbWinUsbA
pi.dll C:\Windows
C:\Android>if /I NOT EXIST C:\Windows\fastboot.exe copy tools\win\fastboot.exe C
:\Windows
C:\Android>if /I NOT EXIST C:\Windows\sleep.exe copy tools\win\sleep.exe C:\Wind
ows
C:\Android>adb shell rm -r /data/local/tmp/*
C:\Android>adb push zergRush /data/local/tmp/zergRush
1726 KB/s (21215 bytes in 0.012s)
C:\Android>adb push misc_version /data/local/tmp/misc_version
1718 KB/s (15837 bytes in 0.009s)
C:\Android>adb shell chmod 777 /data/local/tmp/zergRush
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
C:\Android>adb shell /data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Android>echo Sleeping 10 secs while adb restarts on the device....
Sleeping 10 secs while adb restarts on the device....
C:\Android>sleep 10
C:\Android>adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18
.605.3'
/data/local/tmp/sh: permission denied
C:\Android>adb reboot bootloader
C:\Android>fastboot oem rebootRUU
< waiting for device >
... OKAY [ 0.297s]
finished. total time: 0.297s
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 1.024s]
finished. total time: 1.024s
C:\Android>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra
dio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
sending 'zip' (292817 KB)... OKAY [ 48.610s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 103.258s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.180s
>
I see a lot of people are having trouble downgrading from .98 HBoot, I was also one of those people.
For people that keep getting "error 43" or "error 99" this could potentially fix your problem.
First, I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1298990&highlight=downgrade
Then, I watched this video because sometimes seeing someone do it visually helps me out a little more.
http:// http://m.youtube.com/#/watch?desktop_uri=%2Fwatch%3Fv%3DCgIYFGcVimU&v=CgIYFGcVimU&gl=US
For some reason, even after following these two things, I was still getting those errors. I decided to move the script file (vwhk folder) out of the C:/ location to the actual Platform-tools folder, located in Android-SDK folder.
For me its, C:/android-sdk/platform-tools
Finally, after taking all these steps, I did some more digging around and found out that putting the phone into the bootloader through ADB is what I needed to do, if the regular way wasn't working.
To do this, simply type in "adb reboot bootloader".
Then take the steps to to run the script.
This is what I typed in. (It maybe different for you depending how you have it set up.)
1. cd c:\
2. cd android-sdk
3. cd platform-tools
4. vwhk (hit tab, as it will auto-fill)
5. hack (hit tab again)
6. Sit back and enjoy.
Your links are borked
mastamoon said:
Your links are borked
Click to expand...
Click to collapse
Thanks. Should have working links now.
I have tried to root this incredible 2 but keep getting the error 43. I have turned fastboot off and on, i have put the phone in bootloader. this is not the first phone i have rooted either. what else can i try? below is a copy of my CMD. i have searched google up and down and cannot find a straight answer
C:\Windows\system32>cd c:\
c:\>cd android/android-sdk
c:\Android\android-sdk>hack-vivow.cmd
c:\Android\android-sdk>if /I NOT EXIST C:\Windows\adb.exe copy tools\win\adb.exe
C:\Windows
c:\Android\android-sdk>if /I NOT EXIST C:\Windows\AdbWinApi.dll copy tools\win\A
dbWinApi.dll C:\Windows
c:\Android\android-sdk>if /I NOT EXIST C:\Windows\AdbWinUsbApi.dll copy tools\wi
n\AdbWinUsbApi.dll C:\Windows
c:\Android\android-sdk>if /I NOT EXIST C:\Windows\fastboot.exe copy tools\win\fa
stboot.exe C:\Windows
c:\Android\android-sdk>if /I NOT EXIST C:\Windows\sleep.exe copy tools\win\sleep
.exe C:\Windows
c:\Android\android-sdk>adb shell rm -r /data/local/tmp/*
c:\Android\android-sdk>adb push zergRush /data/local/tmp/zergRush
1294 KB/s (21215 bytes in 0.016s)
c:\Android\android-sdk>adb push misc_version /data/local/tmp/misc_version
1546 KB/s (15837 bytes in 0.010s)
c:\Android\android-sdk>adb shell chmod 777 /data/local/tmp/zergRush
c:\Android\android-sdk>adb shell chmod 777 /data/local/tmp/misc_version
c:\Android\android-sdk>adb shell /data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
c:\Android\android-sdk>echo Sleeping 10 secs while adb restarts on the device...
.
Sleeping 10 secs while adb restarts on the device....
c:\Android\android-sdk>sleep 10
c:\Android\android-sdk>adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_ver
sion -s 2.18.605.3'
/data/local/tmp/sh: permission denied
c:\Android\android-sdk>adb reboot bootloader
c:\Android\android-sdk>fastboot oem rebootRUU
< waiting for device >
... OKAY [ 0.147s]
finished. total time: 0.148s
c:\Android\android-sdk>fastboot erase cache
erasing 'cache'... FAILED (command write failed (No such file or
directory))
finished. total time: 0.000s
c:\Android\android-sdk>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2
.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
< waiting for device >
sending 'zip' (292817 KB)... OKAY [ 49.124s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 93.181s
c:\Android\android-sdk>fastboot reboot
rebooting...
finished. total time: 0.146s
tgjones85 said:
I have tried to root this incredible 2 but keep getting the error 43. I have turned fastboot off and on, i have put the phone in bootloader. this is not the first phone i have rooted either. what else can i try? below is a copy of my CMD. i have searched google up and down and cannot find a straight answer
Click to expand...
Click to collapse
What firmware you on? If it's 6.01.605.05, use the Tacoroot method here.
Update!!!!!!!! Got It! Known Problems,
Thanks to all the devs (to many to name **cough xda**) that do all the hard work to make this possible!!
1. I had to unlock bootloader with HTCDevs first to get root. Then Relock after root. Relock a Must!!
2. No recovery, dont know why just never worked. Tried Fastboot several stock and cwm but no go.
4Ext fastboot flashable found here: http://forum.xda-developers.com/showthread.php?t=1377680
3. The command line used to push the misc_version file. I had to alter it to go through right and take.
4. After that used the vivow hack tool and it worked.
Any ??????? hit me up. Info in thread.
Again thanks to all and credit to all that deserve it!!!!!!!
i have rooted 5 phones. icant get this to take. i have a total of 48 hours over 3 days of trying this. i tired and want to ask for help. i didnt want to ask but i JUST CANT GET THIS!!!!
PLEASE HELP.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Ron>CD..
C:\Users>CD..
C:\>adb push tacoroot.sh /data/local/tacoroot.sh
346 KB/s (2129 bytes in 0.006s)
C:\>adb shell chmod 755 /data/local/tacoroot.sh
C:\>adb push misc_version /data/local
1546 KB/s (15837 bytes in 0.010s)
C:\>adb shell chmod 755 /data/local/misc_version
C:\>adb reboot recovery
C:\>adb shell /data/local/tacoroot.sh --setup
error: device not found
C:\>adb shell /data/local/tacoroot.sh --setup
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
C:\>adb shell /data/local/tacoroot.sh --root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied
C:\>adb reboot bootloader
C:\>fastboot oem rebootRUU
... OKAY [ 0.284s]
finished. total time: 0.285s
C:\>fastboot erase cache
erasing 'cache'... OKAY [ 0.974s]
finished. total time: 0.975s
C:\>fastboot flash zip RUU.zip
sending 'zip' (292817 KB)... OKAY [ 48.947s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 105.528s
C:\>
This is current state. Have been to several other endings. None the right one.
I will pay $$$$$$!!!!!!!
i have xda app on my rooted but locked bootloader electrify if you want to chat.
also have yahoo. [email protected]
google me at [email protected]
call or text me. cell: 2073203065
I am I just tried agian and it ran something really fast and stopped at tags editor, i clicked on exit and the command line now looked like this..
C:\>3
'3' is not recognized as an internal or external command,
operable program or batch file.
C:\>
C:\>11
'11' is not recognized as an internal or external command,
operable program or batch file.
C:\>
C:\>>
The syntax of the command is incorrect.
C:\>
C:\>>>
The syntax of the command is incorrect.
C:\>
C:\>
C:\>
C:\>
C:\>
C:\>
C:\>
C:\>
C:\>Edit Tags
C:\>C:\>3
'C:\' is not recognized as an internal or external command,
operable program or batch file.
C:\>'3' is not recognized as an internal or external command,
''3'' is not recognized as an internal or external command,
operable program or batch file.
C:\>operable program or batch file.
'operable' is not recognized as an internal or external command,
operable program or batch file.
C:\>
C:\>C:\>
The syntax of the command is incorrect.
C:\>C:\>11
'C:\' is not recognized as an internal or external command,
operable program or batch file.
C:\>'11' is not recognized as an internal or external command,
''11'' is not recognized as an internal or external command,
operable program or batch file.
C:\>operable program or batch file.
'operable' is not recognized as an internal or external command,
operable program or batch file.
C:\>
C:\>C:\>
The syntax of the command is incorrect.
C:\>C:\>>
The syntax of the command is incorrect.
C:\>The syntax of the command is incorrect.
'The' is not recognized as an internal or external command,
operable program or batch file.
C:\>C:\>
The syntax of the command is incorrect.
C:\>C:\>>>
> was unexpected at this time.
C:\>The syntax of the command is incorrect.
'The' is not recognized as an internal or external command,
operable program or batch file.
C:\>C:\>
The syntax of the command is incorrect.
C:\>C:\>
The syntax of the command is incorrect.
C:\>C:\>
The syntax of the command is incorrect.
C:\>C:\>
The syntax of the command is incorrect.
C:\>C:\>
The syntax of the command is incorrect.
C:\>C:\>
The syntax of the command is incorrect.
C:\>C:\>
The syntax of the command is incorrect.
C:\>C:\>
The syntax of the command is incorrect.
C:\>C:\>Edit Tags
'C:\' is not recognized as an internal or external command,
operable program or batch file.
C:\>
C:\>C:\>
http://forum.xda-developers.com/showthread.php?t=1751796
Follow the steps exactly. I've done two phones, one with new firmware and one with old and had no problems.
Dermen said:
http://forum.xda-developers.com/showthread.php?t=1751796
Follow the steps exactly. I've done two phones, one with new firmware and one with old and had no problems.
Click to expand...
Click to collapse
Thanks for the quick response Dermen. You have no idea how frustraiting this has been.
Any way you can pm or call me? or just tell me in plain english where to put the files. ihave multiple copies of files in several locations. Or is that the probloem and i should try this on different comp?
EDIT
Tried again and this is where it stops.....
C:\Android>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT1CVMA01862 device
C:\Android>adb push tacoroot.sh /data/local/
cannot stat 'tacoroot.sh': No such file or directory
C:\Android>adb push tacoroot.sh /data/local/
297 KB/s (2129 bytes in 0.007s)
C:\Android>adb shell /data/local/tacoroot.sh --setup
/data/local/tacoroot.sh: permission denied
C:\Android>
Did you make sure your firmware version is 6.01.605.05?
You got permission denied because you skipped a step.
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
adb shell /data/local/tacoroot.sh --setup
Dermen said:
Did you make sure your firmware version is 6.01.605.05?
You got permission denied because you skipped a step.
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
adb shell /data/local/tacoroot.sh --setup
Click to expand...
Click to collapse
THIS WAS MY COMPLETE LAST ATTEMPT..
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Ron>cd..
C:\Users>cd..
C:\>cd Android
C:\Android>adb devices
List of devices attached
HT1CVMA01862 device
C:\Android>adb push tacoroot.sh /data/local/
2 KB/s (2129 bytes in 1.000s)
C:\Android>adb shell chmod 755 /data/local/tacoroot.sh
C:\Android>adb shell /data/local/tacoroot.sh --setup
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
link failed No such file or directory
C:\Android>adb shell /data/local/tacoroot.sh --root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied
C:\Android>adb wait-for-device
C:\Android>adb push misc_version /data/local/tmp/misc_version
protocol failure
C:\Android>adb push misc_version /data/local/tmp/misc_version
2872 KB/s (367096 bytes in 0.124s)
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
C:\Android>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
C:\Android>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
C:\Android>adb shell /data/local/tmp/misc_version -s 2.18.605.3'
Syntax error: Unterminated quoted string
C:\Android>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
C:\Android>adb shell /data/local/tacoroot.sh --undo
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/data/recovery/log, No such file or directory
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
C:\Android>adb reboot bootloader
error: device not found
C:\Android>adb reboot bootloader
error: device not found
C:\Android>adb reboot bootloader
C:\Android>fastboot devices
HT1CVMA01862 fastboot
C:\Android>fastboot getvar mainver
mainver: 6.01.605.05
finished. total time: -0.000s
C:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 0.952s]
finished. total time: 0.952s
C:\Android>fastboot oem rebootRUU
... OKAY [ 0.265s]
finished. total time: 0.265s
C:\Android>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra
dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
sending 'zip' (292817 KB)... OKAY [ 49.374s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 93.584s
C:\
As you can see i am 6.*****
Sorry I couldn't help you, I'm new this stuff. You never answered if your firmware version is 6.01.605.05. If it is lower tacoroot won't work. That's the only thing I know to check.
Dermen said:
Sorry I couldn't help you, I'm new this stuff. You never answered if your firmware version is 6.01.605.05. If it is lower tacoroot won't work. That's the only thing I know to check.
Click to expand...
Click to collapse
Sorry, yes it is 6.01.605.05. in that step in the process you can check it.
C:\Android>fastboot getvar mainver
mainver: 6.01.605.05
finished. total time: -0.000s
I think the prob is this right here.......
"When you get to a screen with a red exclamation mark, press VolUp+Power until you get to a menu, then press VolUp+VolDown+Power until the phone turns off. Once it is rebooted, continue."
I dont ever get to this screen. I think the recovery portion is the problem. i can get to hboot and fastboot and all that. i cant get it to come up with this screen. Think you can help with that?
My phone at that step does not go into recovery, it goes into either hboot or fastboot.
I have no idea what is happening there. Like I said I'm new to this stuff, just got 2 incredible 2s and followed the directions in that thread to root. Maybe somebody who knows will come along and offer some help.
Dermen said:
I have no idea what is happening there. Like I said I'm new to this stuff, just got 2 incredible 2s and followed the directions in that thread to root. Maybe somebody who knows will come along and offer some help.
Click to expand...
Click to collapse
Maybe i will find the answer soon. As of yet still no go. Thanks a bunch for helping out!!
If i can return the favor dont hesitate to hit me up!!
If there is anyone that can shed some light on my issue i would love to hear from you!!!
To all the devs out there please help!!!
I have KFHD 8.9 v8.3. I am having problems getting fastboot working. I have read threads that there are specific "fastboot drivers" and then I have seen other threads where fastboot drivers are a part of the Kindle Fire drivers installed by ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe. No matter what I do I am unable to get "fastboot -i 0x1949 getvar product" to work. At one point I had it rooted with validation from suchecker, still couldnt get fastboot to work, but factory restored to 8.3 to validate steps and instructions and it is a nogo at the moment.
Any help would be appreciated.
So, is your device rooted or not? Your post in another forum seems to contradict what you are saying here.
Liek Soupmagnet said are you positive that your device has root access? If so, I would try wipe the drivers and start from scratch.
As far as I know and it worked for me, fastboot drivers are loaded when you install Android SDK on your PC. See picture bellow.
However in case you need the fastboot drivers you can download here: https://docs.google.com/folder/d/0B4lZEJI5lYeMdzJobG5jSk9QSEk/edit?pli=1 as referenced here: http://forum.xda-developers.com/showpost.php?p=34589184&postcount=6
These ADB drivers worked for me: http://forum.xda-developers.com/showthread.php?t=1890413
For Kindle drivers and Amazon drivers for Windows 8 (if the case),please take a look here: http://forum.xda-developers.com/showthread.php?t=2185402 however I did need not need them.
Is your Kindle showing up when you type the command ADB Devices cmd/terminal window?
I hope it helps.
soupmaget,
I responded to your PM and I said I would try the SoupKit tonight. Calling me out in forums doesn't help you or me and dont know why you keep doing that. I am trying many things but it boils down to the same specific commands. I have even tried the below downloads manually grabbing the commands and typing them in manually.
Last night I refreshed my env following the amazon tutorials step by step. I finally got root by running Root_with_Restore_by_Bin4ry_v25 twice and then Kindle_Fire_Utility_v0.9.6 rooting via recommended option twice. ADB does work, I can "adb reboot", "adb shell" push files, mv files, etc. SUCheck validates I have root.
When I continue to hashchodes TWRP and 2nd bootloader tutorial it states that "you should have working fastboot drivers" which to me means that there is a separate download/driver to install for it to work. I know fastboot.exe is included in the ADK and tried using the other tools for getting fastboot working but its not working.
I do run these with administrative rights....
D:\android\sdk\platform-tools>adb devices
List of devices attached
B0CA060424841KF0 device
So technically this thread is specific to rooting and can be closed as I am passed rooting now and on to fastboot issue...
rwideman said:
So technically this thread is specific to rooting and can be closed as I am passed rooting now and on to fastboot issue...
Click to expand...
Click to collapse
You are blowing my mind right now with your refusal to be helped. Why are you so hell bent on making this difficult for yourself? You have a $300 device that doesn't work and you're being resistant to someone who can most likely help you get it working again. Why? I don't get it...
From what I gather in your various posts, your device is rooted but you cannot access fastboot via the traditional method of entering "fastboot -i 0x1949 getvar product" in the terminal and powering the device up.
Assuming you have a usb/adb/fastboot connection problem with your Mac, you can use SoupKit, but only in certain VMs. But if you have had a previous connection with either fastboot or adb, that probably isn't the case.
Theres a good chance that you can install the Android Terminal Emulator, enter 'su' to gain root privileges and enter "reboot bootloader". That should boot your device into fastboot so you can enter fastboot commands. But, as I told you before, if there is a usb connection problem, and you cannot send fastboot commands to your device, you will be stuck in fastboot. If you have another non-Mac computer available to you, it would be best to boot it into Linux and install soupkit to make sure that doesn't happen. BTW, that is nearly verbatim to what I told you via the first PM.
Are you looking at the timestamps of my postings? Things change over time....
Did you read my PM response? I will try SoupKit tonight, I mentioned this after you told me to try it.
Thank you for your efforts.
My wife took the MBP for the night so I tried 2 old laptops with win7 x64 on them. copied over files and installed the kindle drivers as normal, got KFHD working with adb and then fastboot sits at the prompt waiting just like on my other env, even installed latest jdk 6 and nogo. I am SOL for the day so I will have a drink or 2 tonight and take one of those old laptops to work and install ubuntu 12.10 tomorrow and try again.
Thanks for the help.
FYI, I tried installing the terminal emu and runing "reboot bootloader" with a few fastboot command tries and nogo. I was able to hold the power button and get it to shut off once I got to fastboot mode.
FYI #2, under my previous env with vmware workstation 9 running unbuntu 12.04 in a vm I could not get fastboot to recognize the device but adb was recognizing it perfectly. Trying native ubuntu tomorrow.
FYI #3, In the professional world it is better to stick to non-psychologist bashing, what someone is and is not doing/thinking/acting, and sticking to the issue at hand. I have been in the IT world for 15 years and troubleshooting is my day job (windows, vmware, SAP, *nix, .net, java, j2ee, storage, UCS, routers, switches, nexus, cloud automation, orchestration, etc). Professionalism frowns upon psychologist speak.
rwideman said:
My wife took the MBP for the night so I tried 2 old laptops with win7 x64 on them. copied over files and installed the kindle drivers as normal, got KFHD working with adb and then fastboot sits at the prompt waiting just like on my other env, even installed latest jdk 6 and nogo. I am SOL for the day so I will have a drink or 2 tonight and take one of those old laptops to work and install ubuntu 12.10 tomorrow and try again.
Thanks for the help.
FYI, I tried installing the terminal emu and runing "reboot bootloader" with a few fastboot command tries and nogo. I was able to hold the power button and get it to shut off once I got to fastboot mode.
FYI #2, under my previous env with vmware workstation 9 running unbuntu 12.04 in a vm I could not get fastboot to recognize the device but adb was recognizing it perfectly. Trying native ubuntu tomorrow.
Click to expand...
Click to collapse
You're most likely looking at a driver issue. You might still be able to get them working in Windows. What did you use to install your drivers? Did you use an install package or did you do it manually?
I think I have the same problem. twrp installed on my device, but no OS running, and it can't be recognized on my computer, said driver incorrect, tried so many times, but can't get adb and fastboot work without driver supported. Don't know how to do.
soupmagnet said:
You're most likely looking at a driver issue. You might still be able to get them working in Windows. What did you use to install your drivers? Did you use an install package or did you do it manually?
Click to expand...
Click to collapse
I used these instructions:
https://developer.amazon.com/sdk/fire/connect-adb.html
using ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe
I tried a few different driver sets/packages by different places on the XDA threads but they all ended up being the same driver or detected the KDFHD89 exactly the same.
rwideman said:
I used these instructions:
https://developer.amazon.com/sdk/fire/connect-adb.html
using ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe
I tried a few different driver sets/packages by different places on the XDA threads but they all ended up being the same driver or detected the KDFHD89 exactly the same.
Click to expand...
Click to collapse
When it's in fastboot, do you see anything show up in the device manager?
soupmagnet said:
When it's in fastboot, do you see anything show up in the device manager?
Click to expand...
Click to collapse
Unfortunately no. I haven't had time doing linux with soupkit yet.
I had exactly the.problem still can't get fastboot too see my kindle8.9.
used amrzon driver from sdk.
Adb devices is fine i see the kfhd serial number. .but once use fastboot cmd waiting for device then.never boot in fastboot mode. just boot back to lock screen .This is rooted 8.9 with 8.3 os.
maybe i should do a factory reset.
in order to install a 2nd bootloader and tw-recovery u have to have a rooted kindle hd8.9?
jonahy said:
I had exactly the.problem still can't get fastboot too see my kindle8.9.
used amrzon driver from sdk.
Adb devices is fine i see the kfhd serial number. .but once use fastboot cmd waiting for device then.never boot in fastboot mode. just boot back to lock screen .This is rooted 8.9 with 8.3 os.
maybe i should do a factory reset.
in order to install a 2nd bootloader and tw-recovery u have to have a rooted kindle hd8.9?
Click to expand...
Click to collapse
Yes, you have to be rooted to install the 2nd bootloader and TWRP. I put together the SoupKit so people with driver issues such as yourself can use Linux without much trouble because it is 100 times more reliable than Windows. You should look into it. You can use RootPlus to get root but don't use it to install the 2nd bootloader on 8.3.0 or you will be bricked, likely permanently. But you will be able to use fastboot without any problem to do it manually.
soupkit Folder Empty out
soupmagnet said:
Yes, you have to be rooted to install the 2nd bootloader and TWRP. I put together the SoupKit so people with driver issues such as yourself can use Linux without much trouble because it is 100 times more reliable than Windows. You should look into it. You can use RootPlus to get root but don't use it to install the 2nd bootloader on 8.3.0 or you will be bricked, likely permanently. But you will be able to use fastboot without any problem to do it manually.
Click to expand...
Click to collapse
Hi Thank you for the direction.
I made a Ubuntu 12.10 usbkey booted
then copied ur soupkit folder on desktop Run install.sh ( have to go into permisions check the allow excute)
Run in terminal then terminal show 2 " closed then all the file in soupkit is gone..ha.
didnt see option 1 and 2.
Then i try in Ubuntu termal do abd and fastboot but same as in window 7 KFHD89 just boot into lock screen.
(adb devices it can see devices though
Setting up android-tools-adb (4.1.1+git20120801-1) ...
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9100425160LG8 device)
fastboot not
([email protected]:~$ sudo apt-get install android-tools-fastboot
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
android-tools-fastboot
0 upgraded, 1 newly installed, 0 to remove and 337 not upgraded.
Need to get 48.6 kB of archives.
After this operation, 129 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ quantal/universe android-tools-fastboot i386 4.1.1+git20120801-1 [48.6 kB]
Fetched 48.6 kB in 0s (105 kB/s)
Selecting previously unselected package android-tools-fastboot.
(Reading database ... 161214 files and directories currently installed.)
Unpacking android-tools-fastboot (from .../android-tools-fastboot_4.1.1+git20120801-1_i386.deb) ...
Setting up android-tools-fastboot (4.1.1+git20120801-1) ...
[email protected]:~$ fastboot -i 0x1949 getvar product
< waiting for device >
I was thinking maybe its the Root_with_Restore_by_Bin4ry_v26 mess up somthing? I know my KFHD is rooted it by, but if i load any app need root never show the window ask me if i allow this app in superuser massege.
anyway any tips abot that soupkit Folder Empty out issue?
(just got this tablet last friday, good device so far but put a recovery on it seems a bit harder then my other tablets...But hey I guess thats part of fun too right? )
Thank you in advance.
I think you're confused in how fastboot works. The device must be in fastboot (display says fastboot) in order for fastboot commands to work. There was no need to install android tools. There's a possibility that in doing so you may have made things worse, but we'll see...
Since you have access to adb, try the following command to boot into fastboot:
Code:
adb shell su -c "reboot bootloader"
This, of course, assumes your device is already rooted.
[Edit:] Also, to access Root Plus after installation, enter "rootplus" (without quotes) in the terminal.
Installed 2ND-BOOTLOADER
soupmagnet said:
I think you're confused in how fastboot works. The device must be in fastboot (display says fastboot) in order for fastboot commands to work. There was no need to install android tools. There's a possibility that in doing so you may have made things worse, but we'll see...
Since you have access to adb, try the following command to boot into fastboot:
Code:
adb shell su -c "reboot bootloader"
This, of course, assumes your device is already rooted.
[Edit:] Also, to access Root Plus after installation, enter "rootplus" (without quotes) in the terminal.
Click to expand...
Click to collapse
Great! Got Installed the 2nd bootloader and recovery .
adb shell su -c "reboot bootloader" boot device to fastboot mode.
thanks a lot! SoupMagnet.
Share steps:
D:\sdk\sdk\platform-tools>adb devices
List of devices attached
B0C9100425160LG8 device
D:\sdk\sdk\platform-tools>adb shell su -c "reboot bootloader"
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 getvar product
product: Jem-PVT-Prod-04
finished. total time: 0.006s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/boot of=/sdcard/stock-boot.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.939 secs (8933554 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.937 secs (8952623 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/system of=/sdcard/stock-system.img"
1814528+0 records in
1814528+0 records out
929038336 bytes transferred in 116.782 secs (7955321 bytes/sec)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-boot.img
2794 KB/s (8388608 bytes in 2.931s)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-recovery.img
3008 KB/s (8388608 bytes in 2.723s)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-system.img
3004 KB/s (929038336 bytes in 301.978s)
D:\sdk\sdk\platform-tools>adb push stack /data/local/tmp/
571 KB/s (4096 bytes in 0.007s)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/data/local/tmp/stack of=/dev/b
lock/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "mount -o remount,rw ext4 /system"
D:\sdk\sdk\platform-tools>adb shell su -c "mv /system/etc/install-recovery.sh /s
ystem/etc/install-recovery.sh.bak"
D:\sdk\sdk\platform-tools>adb shell su -c "mount -o remount,ro ext4 /system"
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-
8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.026s]
writing 'bootloader'...
OKAY [ 0.045s]
finished. total time: 0.075s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0
.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.455s]
writing 'boot'...
OKAY [ 0.567s]
finished. total time: 1.030s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-r
ecovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.454s]
writing 'recovery'...
OKAY [ 0.567s]
finished. total time: 1.029s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.004s
D:\sdk\sdk\platform-tools>
FIXED
soupmagnet,
Finally had time to install ubuntu 12.10 on my laptop. I used soupkit for KFHD89 and root-plus from the same posting you had. This worked like a charm. rootplus' version of the play store actually worked compared to other versions I had installed, same for youtube and a few other google apps.
I will toy with TWRP tomorrow. Just glad I got normal google apps installed now.
Hi, I have strange problem After installing lineageos my phone is almost dead.
Problem is I cannot access external SD card from TWRP. I did try to reinstall recovery using fastboot but now it gives error
Code:
c:\adb>fastboot flash recovery twrp-3.0.2-0-find7.img
target reported max download size of 536870912 bytes
sending 'recovery' (10894 KB)...
OKAY [ 0.344s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.355s
After using partition recovery I am having linux icon in the middle, no recovery mode avalible. System boots but I get Encryption error message and reset your phone - where button does not work.
Any Idea how to fix this kind of problem or it is time to buy iphone?
spagg said:
Hi, I have strange problem After installing lineageos my phone is almost dead.
Problem is I cannot access external SD card from TWRP. I did try to reinstall recovery using fastboot but now it gives error
Code:
c:\adb>fastboot flash recovery twrp-3.0.2-0-find7.img
target reported max download size of 536870912 bytes
sending 'recovery' (10894 KB)...
OKAY [ 0.344s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.355s
After using partition recovery I am having linux icon in the middle, no recovery mode avalible. System boots but I get Encryption error message and reset your phone - where button does not work.
Any Idea how to fix this kind of problem or it is time to buy iphone?
Click to expand...
Click to collapse
Iphone? Never ...
Try this.
Edit:
Your device has LVM configured, isn't it? Prior to try to unbrick yo device perhaps you can try to do a full wipe in TWRP and then reflash LVM script
I have the same problem here.
Had CM13 with unified storage. I used coldbird method. I wiped my phone today, and tried to flash LineageOS' latest nightly. Now my Find 7a is stuck at boot screen with the Linux logo in the middle. I have more: After some investigations, I think all the partitions are now screwed. I managed to boot TWRP by runnind "fastboot boot twrp.3.0.2.0.img" and that displays, under storages, something like:
storage 0
storage 1
storage 2
...
storage 20
Recovery partition is missing so I can't flash a new recovery. System partition is there, same as data, and cache...but the phone does not boot.
I tried restoring my backup of coldbirds patition tool with:
adb push DRIVER /tmp
adb push fsc /tmp
adb push fsg /tmp
adb push grow /tmp
adb push LOGO /tmp
adb push misc /tmp
adb push persist /tmp
adb push reserve1 /tmp
adb push reserve2 /tmp
adb push reserve3 /tmp
adb push reserve4 /tmp
adb push ssd /tmp
adb shell
dd if=/tmp/DRIVER of=/dev/block/platform/msm_sdcc.1/by-name/DRIVER
dd if=/tmp/fsc of=/dev/block/platform/msm_sdcc.1/by-name/fsc
dd if=/tmp/fsg of=/dev/block/platform/msm_sdcc.1/by-name/fsg
dd if=/tmp/grow of=/dev/block/platform/msm_sdcc.1/by-name/grow
dd if=/tmp/LOGO of=/dev/block/platform/msm_sdcc.1/by-name/LOGO
dd if=/tmp/misc of=/dev/block/platform/msm_sdcc.1/by-name/misc
dd if=/tmp/persist of=/dev/block/platform/msm_sdcc.1/by-name/persist
dd if=/tmp/reserve1 of=/dev/block/platform/msm_sdcc.1/by-name/reserve1
dd if=/tmp/reserve2 of=/dev/block/platform/msm_sdcc.1/by-name/reserve2
dd if=/tmp/reserve3 of=/dev/block/platform/msm_sdcc.1/by-name/reserve3
dd if=/tmp/reserve4 of=/dev/block/platform/msm_sdcc.1/by-name/reserve4
dd if=/tmp/ssd of=/dev/block/platform/msm_sdcc.1/by-name/ssd
sync
sync
rm /tmp/*
exit
adb reboot
But nothing...when I try to run the swaplayout.bat script which is supposed to revert the unified storage, it does nothing (just reboots the phone...). Does it require the backup files? I read otherwise. Also, this shouldn't be a problem with the partitions layout anyway...I think Lineage OS didn't quite like the unified partitions and broke everything...
any help would be appreciated