Related
I was unsuccessful in my search so I am posting my question in this QA forum.
The original thread was in the Revolution Android Development subforum but I am unable to post on that thread as I am a useless noob.
I have a LG Revolution Android version 2.3.4
I followed the directions as posted:
How Do I Root and Install CWM?:
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!!
I unzipped and was able to update drivers
I was sure to have the USB debugging on (before connecting).
I also set the the USB connection to Internet connection
I clicked root.bat and the following line is repeated almost every other line
'adb' is not recoginized as an internal or external command
At the very end it says:
[*] root complete, enjoy!
[*] Press any key to continue..
When I try to open Titanium backup or Barnacle it says I do not have root
A few other things I'm noticing is that I keep getting usb device not recognized when connecting the phone via usb.
I also noticed a LG software upgrade assistant in my PC tray that I cannot remove.
Any help would be greatly appreciated.
With adb not recognized it sounds like you just ran the root.bat without extracting the zip extract the zip to a folder the click on root.bat
Sent from my VS910 4G using xda premium
Yes, I believe I just unzipped the file and clicked the root.bat. Where do I extract the file to?
Thanks for your response.
Doesn't really matter you just need to extract it you can make a new folder and extract to that
Sent from my VS910 4G using xda premium
Beamer, that certainly did the trick.
Confirmed rooted with access to Barnacle and Titanium.
Now I need to figure out the Gingervolt process. Only about 75 more pages to read through.
Lol if you have clockwork mod recovery just download gingervolt put it on your sd card boot into recovery hold power button down and volume down at the same time until you get to the black screen asking to wipe data or something like that hit the power button to confirm this will not wipe your data but will boot into recovery once in recovery use the volume keys to navigate and power button to select then follow all of the directions in the 1st post every step is important.
Sent from my VS910 4G using xda premium
atlsud said:
Beamer, that certainly did the trick.
Confirmed rooted with access to Barnacle and Titanium.
Now I need to figure out the Gingervolt process. Only about 75 more pages to read through.
Click to expand...
Click to collapse
I appreciate you actually reading instead of instantly asking to be spoon fed!
atlsud said:
I was unsuccessful in my search so I am posting my question in this QA forum.
The original thread was in the Revolution Android Development subforum but I am unable to post on that thread as I am a useless noob.
I have a LG Revolution Android version 2.3.4
I followed the directions as posted:
How Do I Root and Install CWM?:
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!!
I unzipped and was able to update drivers
I was sure to have the USB debugging on (before connecting).
I also set the the USB connection to Internet connection
I clicked root.bat and the following line is repeated almost every other line
'adb' is not recoginized as an internal or external command
At the very end it says:
[*] root complete, enjoy!
[*] Press any key to continue..
When I try to open Titanium backup or Barnacle it says I do not have root
A few other things I'm noticing is that I keep getting usb device not recognized when connecting the phone via usb.
I also noticed a LG software upgrade assistant in my PC tray that I cannot remove.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]
AssumedDarkness said:
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]
Click to expand...
Click to collapse
Here:
http://forum.xda-developers.com/showthread.php?t=1348557
Follow this post, it's as simple as that.
http://forum.xda-developers.com/showthread.php?t=1326542&page=54
It's the easiest to understand for me & worked flawlessly.
Ed
please help
AssumedDarkness said:
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]
Click to expand...
Click to collapse
no im coming up with this and im stuck
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
AssumedDarkness said:
no im coming up with this and im stuck
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
Click to expand...
Click to collapse
Copy and paste the whole thing to pastebin and drop a link in here and I will look at it. That small portion could be normal, I would just have to look at the rest to know for sure.
Sent from my VS910 4G using xda premium
I am trying to root my Revolution 2.3.4 ( I am a complete newb)
How will I know it is rooted?
This is what showed up when it was finished:
Rooting the LG Revolution
Tool Built by mtmichaelson
Exploit Built by the Revolutionary Team
Rooting
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Pushing Zergrush
1279 KB/s (22281 bytes in 0.017s)
Running Zergrush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40121cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd255f1 0xafd39067
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
3639 KB/s (22364 bytes in 0.006s)
3778 KB/s (828156 bytes in 0.214s)
2550 KB/s (843503 bytes in 0.323s)
Removing Trash
Finished Rooting!!!
Press any key to continue . . .
Is that normal?
Is there anything else I need to download on the phone to get rid of bloatware? I am not sure really how to do this.
Thanks!
AprilRevo said:
I am trying to root my Revolution 2.3.4 ( I am a complete newb)
How will I know it is rooted?
This is what showed up when it was finished:
Rooting the LG Revolution
Tool Built by mtmichaelson
Exploit Built by the Revolutionary Team
Rooting
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Pushing Zergrush
1279 KB/s (22281 bytes in 0.017s)
Running Zergrush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40121cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd255f1 0xafd39067
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
3639 KB/s (22364 bytes in 0.006s)
3778 KB/s (828156 bytes in 0.214s)
2550 KB/s (843503 bytes in 0.323s)
Removing Trash
Finished Rooting!!!
Press any key to continue . . .
Is that normal?
Is there anything else I need to download on the phone to get rid of bloatware? I am not sure really how to do this.
Thanks!
Click to expand...
Click to collapse
You are now rooted, I would install CWM and do a back up before doing anything else though.
Sent from my VS910 4G using xda premium
Do I get CWM from the same file as the root?
If so, I did run the "CWM Recovery" from that file. Is that what you mean?
I also see that I am rooted, I downloaded the titinium backup and was able to uninstall a lot of Verizons app that I never use.
Anything else good to do with a rooted Revo?
Gingervolt it !!!! 2.0 is real good & removes all of the bloat. If you find yourself missing anything from the stock that youo want, get the "Stock app installer" & reload what you want...
\Ed
Original post can be found [HERE] [HERE] and [HERE]
Standard disclaimer applies. I am not forcing you to follow this guide or any part thereof you are responsible for anything that you do.
If you find this useful hit the thanks button so I have a reason to keep on keeping on
Thanks to kedriastral, P3Droid, RealBBB, CellZealot, swc2001, Daybreak, and darkstarsinner
From what I hear the 901 radio provides the Bionic with much better reception and will help to alleviate the data drops that are so frequent to many of us. I take no credit for this guide it is more of an extension of the original post.
1) you will need are the drivers.
Bionic 32bit Windows v5.4.0
Bionic 64bit Windows v5.4.0
2) DO A NANDROID3) Proceed with RISK. Proceed with fully charged battery. [this can't be stressed enough, I now have a spare battery and wall charger]
4) Download this Bionic Path Saver 1 Click and unzip it.
5) Navigate into the unziped folder and double click on runmebbb.bat at this point you can follow the script output to see what and when to do it.
[*] Motorola universal root script (Windows version)
[*] by P3Droid * ROOT FIX BY BBB
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to continue after you have changed your USB Mode to Charge Only.
..
Press any key to continue . . .
[*]
[*] Pushing the update zip file to your sdcard...
[*] Do not wipe data or cache...
[*] Pushing 5.5.893...
4412 KB/s (57116385 bytes in 12.641s)
[*] Pushing 5.9.901...
4372 KB/s (59018834 bytes in 13.180s)
[*] Rebooting phone to bootloader...
[*] Press enter to continue if both files pushed to sdcard without an error...
[*] If either file failed to push to device disconnect phone and exit this windo
w...
Press any key to continue . . .
[*] Fastboot flashing needed partitions...
< waiting for device >
sending 'system' (262144 KB)... OKAY [ 18.417s]
writing 'system'... OKAY [ 25.072s]
sending 'system' (229120 KB)... OKAY [ 16.082s]
writing 'system'... OKAY [ 21.371s]
sending 'preinstall' (262144 KB)... OKAY [ 18.110s]
writing 'preinstall'... OKAY [ 23.763s]
sending 'preinstall' (49152 KB)... OKAY [ 3.351s]
writing 'preinstall'... OKAY [ 4.253s]
sending 'webtop' (262144 KB)... OKAY [ 18.132s]
writing 'webtop'... OKAY [ 23.355s]
sending 'webtop' (262144 KB)... OKAY [ 18.196s]
writing 'webtop'... OKAY [ 23.174s]
sending 'webtop' (262144 KB)... OKAY [ 18.215s]
writing 'webtop'... OKAY [ 23.532s]
sending 'webtop' (262144 KB)... OKAY [ 18.394s]
writing 'webtop'... OKAY [ 23.161s]
sending 'webtop' (262144 KB)... OKAY [ 18.860s]
writing 'webtop'... OKAY [ 23.193s]
sending 'webtop' (54016 KB)... OKAY [ 3.736s]
writing 'webtop'... OKAY [ 4.966s]
[*] Rebooting phone...
rebooting...
[*] Rebooting the Phone <------------------| At this point you have to manually boot the phone up by pressing power to turn it off then press and hold vol U+D and power, select normal boot to continue
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
804 KB/s (23056 bytes in 0.028s)
[**] 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 ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000161e0
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40122cd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd19807 0xafd397f7
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
error: device not found
[*] Waiting for phone to reboot.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Attemping persistence...
remount succeeded
1455 KB/s (22364 bytes in 0.015s)
3567 KB/s (1994516 bytes in 0.546s)
3644 KB/s (843503 bytes in 0.226s)
pkg: /data/local/tmp/Superuser.apk
Success
[*] Installing 43v3r Root...
2 KB/s (1501 bytes in 0.528s)
[*] Rebooting...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Installing 5.5.886 BOOT...
3730 KB/s (8388608 bytes in 2.196s)
16384+0 records in
16384+0 records out
8388608 bytes transferred in 9.336 secs (898522 bytes/sec)
[*] Your phone will now restart in recovery, you will need to manually select th
e update893.zip from the menu and install. <------------------| like it says here you have to manually select the update, the recovery screen just looks like a box with a droid until you press the volume keys
[*] If you want to test 5.9.901 install the update901.zip right after you instal
l the update893.zip.
[*] All Done!
Press any key to continue . . .Once all this has been done you can go ahead and check out the 901 patched ROMS.
Just for good measure you should wipe data, cache, dalvik, and format system for all ROMS.
Eclipse V2.0 (.901 Patched)
KINETIX_V1.0_Final SIGNED (.901 OTA Compatible)
Liberty (.901 OTA Compatible)
If you run into problems you should be able to find everything that you need [HERE] if you do use this method the batch file that is included is incomplete, use the one from this post or you will still be BRICK [HERE]
superuser is installed but no root permissions. ROM manager and root checker from the market verified... It appears this method will install superuser but not root privileges.
Decay78 said:
superuser is installed but no root permissions. ROM manager and root checker from the market verified... It appears this method will install superuser but not root privileges.
Click to expand...
Click to collapse
It does root the phone in the .886 stage however once you have updated to .893 you need to rerun the FOR3V3R root hack again in the R3l3AS3D package. At this time use Bionic Bootstrap and put on your CWM Recovery.
After this you will need to Re-boot back into Stock Recovery and flash the .901 update. Once this has been achieved you will have .901 and root will stay.
swc2001 said:
It does root the phone in the .886 stage however once you have updated to .893 you need to rerun the FOR3V3R root hack again in the R3l3AS3D package. At this time use Bionic Bootstrap and put on your CWM Recovery.
After this you will need to Re-boot back into Stock Recovery and flash the .901 update. Once this has been achieved you will have .901 and root will stay.
Click to expand...
Click to collapse
I am stuck on the flash-boot screen nothing is working can someone please help me with better steps to follow
can install the .901OTAzip but then..
the phone reboots and the radio never comes up. I've done it three seperate times (formatted phone, cache, etc.. just to be safe) and it gets to the 'touch android' screen. However the circle with the slash (no radio) remains. It just sits there and says this may take a few minutes blah blah. ANyway I got safely back to .894. wondering if anyone else is having this issue trying to apply the 901ota.zip file
is there an alternate download link for that radio? the megaupload link isnt bionic friendlyy(yes, trying to download directly from phone).
ok so i downloaded this and am already rooted, do i just double-click the " moto-fastboot.exe " file ?
all i really want to do at this point is just update to the new radio
---------- Post added at 12:13 PM ---------- Previous post was at 11:52 AM ----------
alright well, since there weren't instructions here i read on another forum that you have to double-click that 'runmebbb.bat' file. everything seems to be progressing along now although my battery was at 70% when i started so hopefully everything still finishes ok.
ok so i am not rooted running .893 what file do i need to download in order to get on the .901 ??
and is the difference as good as everyone claims that it is
I already did this & got 901. Currently have 'safestrap' installed & running Eclipse. the original OS i accidentally wiped & did not make a backup. Now, if i disable 'safe strap' & try to boot up it just stays at the boot animation and won't do anything else.(but with safe boot enabled, it will boot into eclipse just fine)
If I re-run this all over again will it restore the original OS?
All you need to do is moto-fastboot the system.img and it should work again, but yes rerunning this or using the RSD Lite method with the full FXZ for 5.5.893 will return you to stock again.
That is what these files and methods are intended to do...revert to a completely stock configuration from any modified build. There are some things that cannot be reverted still, like the cdt.bin., so if you go to 5.9.901 then you will need to use that cdt.bin file after reverting with the path saver of the FXZ.
It.s very important to understand how all this works prior to Modding and flashing anything so you know what your options are and you are prepared for unforseen problems.
Otherwise you might end up in a situation where you believe you have to return a device that you destroyed under warranty.
HELP, update did not work phone stuck in boot loop
I just tried to apply this update and it fails at the Webtop flash part of the script. The command is "moto-fastboot flash webtop grfs.img" and it fails with "load_file: could not allocate 1397489664 bytes error: cannot load 'grfs.img'". I have seen other users with this error, but have not found a fix. I know it has nothing to do with the phone itself because I can produce this error with the phone disconnected, but when I run "moto-fastboot flash preinstall preinstall.img" it WAITS for the phone to connect. I then thought maybe the grfs.img file was corrupted and downloaded the ZIP from mydroidworld, but I still have the same issue. The phone is now stuck in a boot loop. How can I fix this?
Terror_1 said:
Original post can be found [HERE] [HERE] and [HERE]
Standard disclaimer applies. I am not forcing you to follow this guide or any part thereof you are responsible for anything that you do.
If you find this useful hit the thanks button so I have a reason to keep on keeping on
Thanks to kedriastral, P3Droid, RealBBB, CellZealot, swc2001, Daybreak, and darkstarsinner
From what I hear the 901 radio provides the Bionic with much better reception and will help to alleviate the data drops that are so frequent to many of us. I take no credit for this guide it is more of an extension of the original post.
1) you will need are the drivers.
Bionic 32bit Windows v5.4.0
Bionic 64bit Windows v5.4.0
2) DO A NANDROID3) Proceed with RISK. Proceed with fully charged battery. [this can't be stressed enough, I now have a spare battery and wall charger]
4) Download this Bionic Path Saver 1 Click and unzip it.
5) Navigate into the unziped folder and double click on runmebbb.bat at this point you can follow the script output to see what and when to do it.
[*] Motorola universal root script (Windows version)
[*] by P3Droid * ROOT FIX BY BBB
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to continue after you have changed your USB Mode to Charge Only.
..
Press any key to continue . . .
[*]
[*] Pushing the update zip file to your sdcard...
[*] Do not wipe data or cache...
[*] Pushing 5.5.893...
4412 KB/s (57116385 bytes in 12.641s)
[*] Pushing 5.9.901...
4372 KB/s (59018834 bytes in 13.180s)
[*] Rebooting phone to bootloader...
[*] Press enter to continue if both files pushed to sdcard without an error...
[*] If either file failed to push to device disconnect phone and exit this windo
w...
Press any key to continue . . .
[*] Fastboot flashing needed partitions...
< waiting for device >
sending 'system' (262144 KB)... OKAY [ 18.417s]
writing 'system'... OKAY [ 25.072s]
sending 'system' (229120 KB)... OKAY [ 16.082s]
writing 'system'... OKAY [ 21.371s]
sending 'preinstall' (262144 KB)... OKAY [ 18.110s]
writing 'preinstall'... OKAY [ 23.763s]
sending 'preinstall' (49152 KB)... OKAY [ 3.351s]
writing 'preinstall'... OKAY [ 4.253s]
sending 'webtop' (262144 KB)... OKAY [ 18.132s]
writing 'webtop'... OKAY [ 23.355s]
sending 'webtop' (262144 KB)... OKAY [ 18.196s]
writing 'webtop'... OKAY [ 23.174s]
sending 'webtop' (262144 KB)... OKAY [ 18.215s]
writing 'webtop'... OKAY [ 23.532s]
sending 'webtop' (262144 KB)... OKAY [ 18.394s]
writing 'webtop'... OKAY [ 23.161s]
sending 'webtop' (262144 KB)... OKAY [ 18.860s]
writing 'webtop'... OKAY [ 23.193s]
sending 'webtop' (54016 KB)... OKAY [ 3.736s]
writing 'webtop'... OKAY [ 4.966s]
[*] Rebooting phone...
rebooting...
[*] Rebooting the Phone <------------------| At this point you have to manually boot the phone up by pressing power to turn it off then press and hold vol U+D and power, select normal boot to continue
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
804 KB/s (23056 bytes in 0.028s)
[**] 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 ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000161e0
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40122cd4 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd19807 0xafd397f7
[*] Sending 181 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
error: device not found
[*] Waiting for phone to reboot.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Attemping persistence...
remount succeeded
1455 KB/s (22364 bytes in 0.015s)
3567 KB/s (1994516 bytes in 0.546s)
3644 KB/s (843503 bytes in 0.226s)
pkg: /data/local/tmp/Superuser.apk
Success
[*] Installing 43v3r Root...
2 KB/s (1501 bytes in 0.528s)
[*] Rebooting...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Installing 5.5.886 BOOT...
3730 KB/s (8388608 bytes in 2.196s)
16384+0 records in
16384+0 records out
8388608 bytes transferred in 9.336 secs (898522 bytes/sec)
[*] Your phone will now restart in recovery, you will need to manually select th
e update893.zip from the menu and install. <------------------| like it says here you have to manually select the update, the recovery screen just looks like a box with a droid until you press the volume keys
[*] If you want to test 5.9.901 install the update901.zip right after you instal
l the update893.zip.
[*] All Done!
Press any key to continue . . .Once all this has been done you can go ahead and check out the 901 patched ROMS.
Just for good measure you should wipe data, cache, dalvik, and format system for all ROMS.
Eclipse V2.0 (.901 Patched)
KINETIX_V1.0_Final SIGNED (.901 OTA Compatible)
Liberty (.901 OTA Compatible)
If you run into problems you should be able to find everything that you need [HERE] if you do use this method the batch file that is included is incomplete, use the one from this post or you will still be BRICK [HERE]
Click to expand...
Click to collapse
Here is the link to the latest Eclipse Rom. This Rom is actually built on .901
It is version (Eclipse 2.1 RC1) Donate to Nitro He is AWESOME!!
I had multiple problems with this update so I put together the method I used to get my phone up and running... enjoy.
http://forum.xda-developers.com/showthread.php?p=21514430
trackie said:
I upgraded to 901 but lost root. I have stock recovery. How do i go back to 893?
Click to expand...
Click to collapse
This site is a gold mine. Fixed my problem. Thanks for the wealth of information and everyone's hard work posting these guides
.901 + safestrap + enabled = no boot
Liberty3 + .901 = boot loop
Fyi thanks rooted on .901 atleast
Sent from my DROID BIONIC using XDA App
Slie said:
.901 + safestrap + enabled = no boot
Liberty3 + .901 = boot loop
Fyi thanks rooted on .901 atleast
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
If you're rooted on .901 all you need is Clockwordmod and Liberty3 2.0 (.901 patched). If you use the normal Liberty3 2.0 ZIP you WILL have issues because it isn't setup to support the .901 radio.
Thanks I double checked that i was using the correct build.
I just don't know why I cant boot with the safe system enabled on stock, or with the custom rom.
I grabbed the patched.901.liberty file again but i have a feeling it will have the same results. I'm stoked i upgraded for this rom. I couldn't go back the the older radio's the newer ones are so much better. So much..
Any suggestions on either issues would be great.
Im on stock rooted(43v3r) .901 and is confirmed.
Sent from my DROID BIONIC using XDA App
Slie said:
Thanks I double checked that i was using the correct build.
I just don't know why I cant boot with the safe system enabled on stock, or with the custom rom.
I grabbed the patched.901.liberty file again but i have a feeling it will have the same results. I'm stoked i upgraded for this rom. I couldn't go back the the older radio's the newer ones are so much better. So much..
Any suggestions on either issues would be great.
Im on stock rooted(43v3r) .901 and is confirmed.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Let me know if you can flash. You definately should be able to...
Okay, so this morning tried it multiple times no go.
Only thing I did different this time was leave the file on my internal sdcard and flash.
All good finally back on liberty,
Thank you a bunch.
.901 + safemode + enabled = Liberty
EDIT: is it supposed to say I'm back on 5.5.886,
Sent from my DROID BIONIC using XDA App
Slie said:
Okay, so this morning tried it multiple times no go.
Only thing I did different this time was leave the file on my internal sdcard and flash.
All good finally back on liberty,
Thank you a bunch.
.901 + safemode + enabled = Liberty
EDIT: is it supposed to say I'm back on 5.5.886,
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Good to hear. I have the same version information, but my radio issues have pretty much gone away. Also, Liberty cannot flash the radio so there is no way it could downgrade it.
Hi!
I'm trying to root my XZ with new .253 firmware. I repeated the procedure which I know well from my XS (I did it there several times, always with success): dumping system.sin from ftf, extracting ext4 with sin2raw, loopmounting it, adding su and Superuser.apk, creating new img with make_ext4fs and finally flashing it with fastboot.
But now, I'm stuck here:
Code:
[email protected]:/home/patrol/sxs# FlashTool/x10flasher_lib/fastboot.linux flash system ./system.img
< waiting for device >
sending 'system' (1111575 KB)...
FAILED (remote: data too large)
finished. total time: 0.002s
It looks that the phone refuses to load such a long data - but it's just a few kilobytes longer than the original one... Of course I'm using -s option to make_ext4fs, otherwise it would be almost twice as long (I suppose that the /system is 2GB)... And forgot to say my BL is unlocked... I've tried about 4 different fastboot binaries (two of them compiled by myself, the last one coming from the latest FlashTool/Linux beta package... Any help ?
With regards,
Pavel
Today's news: I continued with experiments. I've tried to remove files from the fs to decrease the size below 1G. However, the same thing appeared, just the reported size was 998239 K. So, 1G is not any magic boundary .
tl;dr Android OS is missing from my Nexus 6 for an unknown reason, fastboot isn't working (nor is flashing via recovery), /system and /firmware partitions read 0 MB in each. Help!
Context
My Nexus 6 is a replacement I got in the beginning of February after some speaker issues with my original N6. The device was unlocked, encrypted, used TWRP as custom recovery, and rooted (with Chainfire's SuperSU). I was running stock 5.1 (shamu-lmy47d). My root apps were few: AdAway, TitaniumBackup, SuperSU, Solid Explorer, and Cerberus (no account activity with Cerberus in the past two weeks). I'm familiar with fastboot, custom recoveries, flashing, etc. I've been doing this on my Droid X, Nexus 4, Nexus 7, and Nexus 6 for years and never had anything like this happen (nor have I really run into issues I couldn't figure out).
Situation
While using Sync for Reddit, some apps started crashing. Then Sync stopped loading anything. Then seemingly every app on my device reported a crash. Thinking a reboot would fix whatever was going on, I rebooted my phone. The boot animation didn't end after ten minutes, so I shut my phone back off and got into recovery.
I tried rebooting to system from TWRP. The first thing I noticed was that TWRP did not prompt me for a PIN. When I tried rebooting to system, I was greeted with the following message: "No OS installed! Are you sure you wish to reboot?". Confused, I went to the backup page to check partition sizes. TWRP showed "System (0MB)", "Data (56975MB)" (that's 57GB--I probably had 20GB maximum).
TWRP logs read as follows:
Code:
Data successfully decrypted, new block device '/dev/block/dm-0'
Updating partition details...
[COLOR="Red"]E:Unable to mount '/system'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage[/COLOR]
Successfully decrypted with default password.
Updating partition details...
[COLOR="Red"]E:Unable to mount '/system'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.[/COLOR]
Full SELinux support is present.
[COLOR="red"]E:TWFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to open '/cache/recovery/.version'.
E:Unable to mount '/data'[/COLOR]
MTP Enabled
A factory reset from TWRP returns the following:
Code:
Factory Reset Complete
[COLOR="red"]Failed[/COLOR]
and in the log:
Code:
[COLOR="red"]E:Unable to mount '/data'
E: Unknown MTP message type: 1[/COLOR]
Formatting Cache using make_ext4fs function.
[COLOR="red"]E:Unable to mount '/cache'[/COLOR]
Updating partition details...
[COLOR="red"]E:unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/firmware'[/COLOR]
...done
[COLOR="red"]E:Unable to mount storage.[/COLOR]
I will now post the results of several fastboot commands. Some analysis will follow at the end of this post, but I don't really have a clue as to what is going on.
Code:
$ fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (522112 KB)...
OKAY [ 17.483s]
writing 'system'...
OKAY [ 8.162s]
sending sparse 'system' (510197 KB)...
OKAY [ 17.036s]
writing 'system'...
OKAY [ 7.362s]
sending sparse 'system' (515601 KB)...
OKAY [ 17.891s]
writing 'system'...
OKAY [ 8.047s]
sending sparse 'system' (188485 KB)...
OKAY [ 6.661s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 94.184s
Code:
$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to flash partition
FAILED (remote failure)
finished. total time: 6.105s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.676s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 13.678s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: moto-apq8084-71.08
Baseband Version.....: D4.0-9625-02.95
Serial Number........: ZX1G322CNQ
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (7681 KB)...
OKAY [ 0.243s]
writing 'boot'...
(bootloader) Failed to flash partition boot
(bootloader) Failed to flash partition boot
FAILED (remote failure)
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
Code:
$ fastboot -w
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.758s
Code:
$ fastboot format system
formatting 'system' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.002s
I'll try any suggested commands as nothing appears to be working anyways. At this point, I don't care about my data. It's encrypted anyways, so it's probably unrecoverable regardless of if I get my phone working again.
I think the partition table somehow got destroyed or the flash memory failed. What's curious is that /data, /boot, /recovery, /EFS are still intact while /firmware and /system are not. I blame hardware because the issues started while the OS was booted (what on the OS level has permissions to write to /system and /firmware?) and nothing writes to the partitions anymore (they can't even be mounted!).
I'm looking for help in any way, especially the in the following:
(1): Finding the cause of this issue and squashing it if it's a bug in Android, TWRP, or some other software.
(2): Getting my phone back to a working state. Again, I don't care about the data on the device.
(3): (if 2 fails) getting my phone locked and removing TWRP so that I can RMA it--Google has already offered a replacement, but I don't want to send it in unlocked and with TWRP (may cause them to charge me for the replacement)
If this is indeed a software-caused error (again, I don't think my actions of using Sync for Reddit caused this issue), I'm terrified that this may affect others who are less capable of seeking help, or those who have critical data on their devices.
Thanks for reading. Please offer any guidance you may have.
-Ethan
kudos to you for providing so much detail for your problem. It's a rare sight here. It really helps people who are trying to help you.
I have a feeling your device is completely fried as even fastboot isn't working. I remember I had a similar problem with the OS disappearing but I solved it with a fastboot flash. If that doesn't work for you, I'm not sure what can. But then again, I'm not a seasoned tinkerer when it comes to android partitions. Let's wait for someone with more knowledge to share their opinion.
@rootSU do you have any ideas here? Can he mount in TWRP and possibly push the files needed or is TWRP too broken at this point?
Thank you for providing such details with the errors. I wish everyone was so thorough.
Thanks for the replies so far @exb0 and @Evolution_Freak!
For the record, "fastboot devices" and "adb devices" do work. It just appears that any thing operating on the file system does not work. Strangely, I was able to "adb push" a ZIP over and tried to flash it from recovery (flashing failed, of course). I was also able to move the ZIP around using TWRP.
I wonder if it would be feasible to move files into place manually and get a working system again by doing that. I don't want to do that unless it appears to be my only option and there's a good chance of it actually working.
I don't frequent XDA, so help getting knowledgeable community members would be greatly appreciated.
Even if you got it working, if it went *this* bad, you don't want the risk of futures failure. Flash as much stock as you can after formatting each partition using fastboot and return it.
rootSU said:
Even if you got it working, if it went *this* bad, you don't want the risk of futures failure. Flash as much stock as you can after formatting each partition using fastboot and return it.
Click to expand...
Click to collapse
Good point. I think my plan is to get it back to a locked state without TWRP. But how to get there, I have no idea. As you can see in the logs, I can't flash anything with fastboot :\ How can I format the partitions? I might be able to do that.
ethanmad said:
Good point. I think my plan is to get it back to a locked state without TWRP. But how to get there, I have no idea. As you can see in the logs, I can't flash anything with fastboot :\ How can I format the partitions? I might be able to do that.
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
You can try and also:
fastboot format system
fastboot format userdata
fastboot format cache
See if you can then flash system.img, userdata.img and cache.img separately.
Also, which version of adb/fastboot are you using? if you are using the one from the Android SDK i would recommend running the sdk update manager and making sure the SDK platform tools are the latest version
@rootSU I believe the OP already tried "fastboot format system" and got the error "Formatting is not supported for filesystem with type 'raw'."
Didgeridoohan said:
@rootSU I believe the OP already tried "fastboot format system" and got the error "Formatting is not supported for filesystem with type 'raw'."
Click to expand...
Click to collapse
Yes, it says in his post
I will add this, do NOT attempt to OEM lock again. I'm glad it had failed when you tried. Otherwise, we would already be done here.
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
---------- Post added at 07:25 AM ---------- Previous post was at 06:50 AM ----------
Did some searching and found this:
https://help.ubuntu.com/community/DataRecovery
However, being that you've already tried writing to the damaged partitions, it might not be of any help.
---------- Post added at 07:45 AM ---------- Previous post was at 07:25 AM ----------
Not even sure that those tools would apply here but this seems to be a very rare or random error you've encountered.
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
SFVDan said:
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
Click to expand...
Click to collapse
I had initially thought of this but his phone is still recognized by a PC as it normally should be and not as qhusb bulk. But if this could be a possible solution to his partition problem, then thank you for pointing him in that direction. :good:
IINexusII said:
Also, which version of adb/fastboot are you using? if you are using the one from the Android SDK i would recommend running the sdk update manager and making sure the SDK platform tools are the latest version
Click to expand...
Click to collapse
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
Evolution_Freak said:
I will add this, do NOT attempt to OEM lock again. I'm glad it had failed when you tried. Otherwise, we would already be done here.
Code:
$ fastboot oem lock
...
(bootloader) Failed to erase partition
(bootloader) General Lock failure!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 11.836s
---------- Post added at 07:25 AM ---------- Previous post was at 06:50 AM ----------
Did some searching and found this:
https://help.ubuntu.com/community/DataRecovery
However, being that you've already tried writing to the damaged partitions, it might not be of any help.
---------- Post added at 07:45 AM ---------- Previous post was at 07:25 AM ----------
Not even sure that those tools would apply here but this seems to be a very rare or random error you've encountered.
Click to expand...
Click to collapse
What's wrong with running oem lock? What damage would it do?
I'll try using that link when I get home.
And the error is very strange, yes.
SFVDan said:
I am no expert, but the concept about reflashing the default partition table contained in this thread may be helpful. I am not fluent enough in this to advise, but given the detail with which you posed your OP, I figgered you would have no trouble making sense of this:
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Edit: Look for an explanation of GPT.bin.
Click to expand...
Click to collapse
Thanks, that looks like it might help. I'll try when I get home. To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
@opssemnik is this is a similar issue to what your post is about? I'm not quite sure what qhusb_bulk means, but my phone is recognized as "Nexus 6" in the file explorer and fastboot/adb devices show the device.
ethanmad said:
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
What's wrong with running oem lock? What damage would it do?
I'll try using that link when I get home.
And the error is very strange, yes.
Thanks, that looks like it might help. I'll try when I get home. To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
@opssemnik is this is a similar issue to what your post is about? I'm not quite sure what qhusb_bulk means, but my phone is recognized as "Nexus 6" in the file explorer and fastboot/adb devices show the device.
Click to expand...
Click to collapse
Had your OEM lock succeeded, with no OS installed, you could have inadvertently bricked yourself. It's in your best interest to leave it unlocked until you're sure you can boot into Android and ensure that the "allow OEM unlock" stays ticked after a reboot. If you'd like more information on that, click the top link in my signature.
First things first though, let's get you up and running.
ethanmad said:
To be honest, the detail in the post is not indicative of my knowledge level. I just copied and pasted (or typed out) logs and command results.
Click to expand...
Click to collapse
That you knew enough to do so IS indicative -- at least from my perspective. Well done! Keep us all posted.
ethanmad said:
ADB is version 1.0.31. Fastboot is 4.2.2+git20130218-3ubuntu23, which is the latest version on Ubuntu 14.04. I think my SDK platform tools are up-to-date, but I'll make sure to update when I get home.
Click to expand...
Click to collapse
Just as an FYI, the most current version of ADB is 1.0.32. The Ubuntu repositories do not contain the up to date version.
Louie998 said:
Just as an FYI, the most current version of ADB is 1.0.32. The Ubuntu repositories do not contain the up to date version.
Click to expand...
Click to collapse
Correct. I had to download and install the full SDK to get the latest version. Couldn't flash the OTA with the version that was available from Ubuntu repositories.
If this just happened out of the blue, your internal storage probably has (hardware) issues, flash back stock boot and recovery and return it. Unless you have some data you really want to recover, what's the point of trying to fix it? You can never trust this device again.
Chainfire said:
If this just happened out of the blue, your internal storage probably has (hardware) issues, flash back stock boot and recovery and return it. Unless you have some data you really want to recover, what's the point of trying to fix it? You can never trust this device again.
Click to expand...
Click to collapse
That's part of the problem, he can't get anything to flash. Everything attempted errors out.
Lineage 17.1 for the Sony Xperia 10 II
Please note this is currently for the dual-sim model ONLY. When you need a single-sim variant leave a comment, so we can work an that...
Code:
/*
* Disclaimer - your warranty may be void.
*
* I'm not responsible for bricked devices, dead OTGs or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Features
OTA updates - always delayed for 1 day (to prevent broken rollouts); when you want it immediately, checkout my GitLab pipelines
Increased volume steps to 25
Over-provisioned system image (580MiB), to allow install of OpenGApps and other stuff
Open Source (it is based on SODP, you can view all my patches and ci scripts here or here)
Package signature spoofing (needed by MicroG)
What does not work?
Stock camera app with wide and zoom cameras, you may use Open Camera to circumvent that.
Notification LED blinking - kernel driver bug (see here)
LiveDisplay
You tell me...
Download
There you have multiple options:
To get the complete package (both including the ota and imgparts; only needed for the initial setup) visit...
AndroidFileHost
GitLab (make sure to download the artifacts from the master branch)
To get ONLY the OTA package to update your system later on, visit (or open up the LineageOS Updater) ota.simonmicro.de - please note that only the last recent 14 days are accessible there.
Changelog
2021-02-28
Fixed wifi hotspot.
2020-12-18
Fixed cameras.
2020-11-27
Fixed ADB security.
2020-11-25
Added SELinux support.
2020-11-20
Added OpenGApps support.
2020-11-17
Initial release.
How to install your system
The following guide assumes, you have setup adb and fastboot already (make sure to always use the latest version of the toolkit, otherwise you'll may get problems during flashing) - for that take a look into the internet. Also you should already downloaded the complete package from above!
Unlock the bootloader - a "how to" is here...
Download the oem binaries from here, make sure to use exactly that version!
Boot into the bootloader (hold "Volume up + Insert the USB cable" until led lights blue) and then update the oem partition:
Code:
fastboot flash oem_a [EXTRACTED_OEM_IMAGE_FILE]
fastboot flash oem_b [EXTRACTED_OEM_IMAGE_FILE]
Flash now the Lineage recovery partition as well as the dtbo partition (they are inside the img folder of the complete package):
Code:
fastboot flash recovery [EXTRACTED_RECOVERY_IMAGE_FILE]
fastboot flash dtbo [EXTRACTED_DTBO_IMAGE_FILE]
Disable the verity checks for now, as your new recovery violates the Sony verity profiles of the Stock ROM:
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
Okay, you are now ready to boot the first time into the Lineage recovery, unplug the phone NOW!
To boot into recovery: Hold "Volume down + Power" until it vibrates...
You should now be booted into the recovery. We now clean any old data from Sonys Stock ROM - this is just to make sure you have a really clean install: Choose the "Factory reset" option.
The phone is now clean and ready to accept the new system. You now can either install just the OTA package and be done or flash every .img from the full package manually - the coice is yours. When you plan to flash the images manually, make sure to include boot, system, product, vendor, vbmeta_system, as these are normally part of the OTA update (I extracted the payload.bin to verify this!). For the latter approach you may orient yourself on my flashall.sh. I'll choose the simpler OTA-sideload approach for now.
Select "Apply update -> Apply from ADB" (now make sure the adb server runs as root - may use adb kill-server && sudo adb start-server to fix that) and execute (the OTA zip is inside the ota subdir):
Code:
adb sideload [OTA_SYSTEM_UPDATE_ZIP_FILENAME]
Something went wrong - help!
(Step 7-8) When you now see a device corrupt error
Don't panic!
You messed up the verity disable step from before - try again.
Try to switch the current boot slot (get current fastboot getvar current-slot and set new fastboot --set-active=, you can choose between a and b) and retry disableing verity disable again!
When your device fails to boot too many times (and crashes) the current slot could also get marked as corrupt. To reset that counter you'll need to reflash the boot partition - to see what is going on, try fastboot getvar all and look out for something like a unbootable flag.
(Step 9) When you get Operation not permitted during flashing
This is commonly caused by relocking and then reunlocking the bootloader (yay - buggy firmware). You'll need to relock, restore (and boot) the device with Flashtool using Sonys original ROM and start from fresh.
(Step 10) When you get the kDownloadPayloadPubKeyVerificationError error
Well, that's caused by using an other recovery than the provided one, as I use my own private keys to sign the build the recovery must also know them. Using an other recovery than the one from
the img folder of the complete package will most likely not include them (and when they do - I am in big trouble), and therefore fail. But you are in luck: It seems that the recovery writes
the data to the currently inactive slot and then fails. You could simply switch the system slot like described above!
Want to install Magisk?
Install the Magisk zip like the OTA system update by using adb sideload [MAGISK_FILE_NAME].
Want to install OpenGApps?
Make sure to use the pico-variant, as the system partition is even with over-provisioning really small (as the installer extracts some more stuff on the first boot) - then install the OpenGApps zip like the OTA system update by using adb sideload [OPENGAPPS_FILE_NAME].
Credits
As much I would like, I can't do everything by myself. A huge thank you to...
@MartinX3 for the used local_manifests and his device tree from his LineageOS organization
...the team behind @sonyxperiadev, for their great work (and their kernel sources)!
XDA:DevDB Information
LineageOS 17.1 for pdx201, ROM for the Sony Xperia 10 II
Contributors
Simonmicro, MartinX3
Source Code: https://gitlab.simonmicro.de/android/lineage/lineage-pdx201
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Sony OEM Package
Based On: AOSP
Version Information
Status: Beta
Hey,
as you guys may have already noted, I have stopped the active development phase for this LOS port a while ago. This was caused by me just not having enough time to do everything and additionally maintain a LOS port.
Today I'll upload the last maintenance build to the OTA server and mirrors. Of course I somehow included a little bug, which causes the system to complain about "an internal problem", which seem to be caused by some interaction with the OpenGApps package installer. Now, it is a feature. I'll may post one more update, if I figure this one out.
Nevertheless, I'll shut down the OTA service at 2022-06-01 (see https://status.simonmicro.de) and will then archive all project data. It was a great time to learn many (new/nasty) things about Android and how everything works. I have to say "thank you" to everyone, who supported me and was on board with this project.
See you next time,
simonmicro
-> https://forum.xda-developers.com/t/...r-xperia-10-ii-ota-sodp.4191601/post-86352693 <-
Reserved
First
At last The guide, source code looks great! Will install, check it next
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
bamdadkhan said:
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
Click to expand...
Click to collapse
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Simonmicro said:
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Click to expand...
Click to collapse
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
bamdadkhan said:
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
Click to expand...
Click to collapse
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Simonmicro said:
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Click to expand...
Click to collapse
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Thapsus-cz said:
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Click to expand...
Click to collapse
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Click to expand...
Click to collapse
See full log for flashing images:
sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
[sudo] пароль для :
Sending 'boot_b' (65536 KB) OKAY [ 2.441s]
Writing 'boot_b' OKAY [ 0.358s]
Finished. Total time: 2.812s
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'product' (432072 KB) OKAY [ 16.440s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vendor' (48084 KB) OKAY [ 1.725s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta_system' (4 KB) OKAY [ 0.005s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.016s
❯ sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
❯ sudo fastboot flash boot boot.img
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash product product.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash super_empty super_empty.img
sudo fastboot flash system system.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash vbmeta_system vbmeta_system.img
sudo fastboot flash vendor vendor.img
Sending 'boot_b' (65536 KB) OKAY [ 2.438s]
Writing 'boot_b' OKAY [ 0.378s]
Finished. Total time: 2.831s
Sending 'dtbo' (8192 KB) OKAY [ 0.302s]
Writing 'dtbo' OKAY [ 0.046s]
Finished. Total time: 0.357s
Sending 'product' (432072 KB) OKAY [ 16.212s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.699s]
Writing 'recovery' OKAY [ 0.557s]
Finished. Total time: 4.265s
Sending 'super_empty' (4 KB) OKAY [ 0.011s]
Writing 'super_empty' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.755s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.021s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.014s
Sending 'vendor' (48084 KB) OKAY [ 1.770s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Click to expand...
Click to collapse
xdauserart said:
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
See full log for flashing images:
Click to expand...
Click to collapse
I had the same problem yesterday with the same results. I struggled with it until morning. Eventually I downloaded the latest version of adb, flashed the stock rom again and started over. It was done in twenty minutes. Try the latest version of adb (I guess version 35 for Windows)
xdauserart said:
Done till the step 9.
Click to expand...
Click to collapse
...
Code:
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
This indicates you tried to use the bootloader (which also has fastboot support) to flash the images. I made sure to write the guide the way that it states you should use the fastbootd service of the recovery. I have the dumb feeling that many more will go your way and fail. Damn it.
Code:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Is fine, as you just erased all data - this also kills the partion so it cant be mounted anymore (that's the errors). This is indeed intentional as the system is now forced to really start fresh!
xdauserart said:
Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds"
Click to expand...
Click to collapse
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Two PR to fix back triple cam. But front cam is still broken.
https://github.com/sonyxperiadev/device-sony-seine/pull/29
https://github.com/sonyxperiadev/device-sony-pdx201/pull/15
--------------EDIT-----------------
Switch to CAF powerhal, better performance we have.
https://github.com/sjllls/device-sony-common/commit/de3b2bbbc33130891263d9e81ea2178a0f6783c4
https://github.com/sjllls/device-sony-sepolicy/commit/72059258eb0ff2c854996a05a5a23a8b73b55459
--------------EDIT-----------------
Renmember to let users flash with latest platform-tools, or they could not boot because of logical partition is not resized.
https://developer.android.com/studio/releases/platform-tools
Simonmicro said:
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Click to expand...
Click to collapse
I can confirm that Opengapps pico can now be installed without a bootloop. I'm at work and I don't have adb. I installed them directly as an update from the sd card using recovery. Everything works fine.
Can we get OpenGapps Nano support?
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
KriiXOne said:
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
Click to expand...
Click to collapse
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Simonmicro said:
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Click to expand...
Click to collapse
I'll try tomorrow after the math test that i'm studying for today, and will let ya know ^^'
Simonmicro said:
...
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Click to expand...
Click to collapse
Fixed it Just repeated the steps from the first one and used OTA on step 9. Thanks!