This one is deprecated! Please use this one instead.
Some words about...
This recovery is for amami - Sony Z1 compact.
I'm opening this thread because I was looking for an up-to-date version of TWRP recovery. After a long search i found this one: https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/lineageos-12-1-z1c-current-sec-patches-t3614936.
Why am I opening this thread then?
Well,
I want to built TWRP from newest android sources (not like cm12.1 that is used in the link above )
and I want to get a deeper understanding of sony's partition layout (especially concerning recovery).
I just read a comment about the possibilities to store a recovery on our device, but unfortunately I couldn't find it again. It was something like that:
fastboot flash boot boot.img (recovery uses same kernel but different ramdisk, common sony approach, after kernel boot-up hardware keys decide which ramdisk to load)
fastboot flash FOTAKernel recovery.img (recovery is stored on extra partition with own kernel and own ramdisk)
fastboot flash recovery recovery.img (recovery is stored on extra partition with own kernel and own ramdisk)
So I stumbled over https://forum.xda-developers.com/showpost.php?p=73575131&postcount=130 and followed the instruction. But an inspection of the partitions leads me to the following assumption: either the thing doesn't worked - or fastboot flash FOTAKernel recovery.img and fastboot flash recovery recovery.img are doing the same thing.
The partitions afterwards:
Code:
major minor #blocks name #label
254 0 524288 zram0
179 0 15267840 mmcblk0
179 1 2048 mmcblk0p1 TA
179 2 512 mmcblk0p2 sbl1
179 3 256 mmcblk0p3 s1sbl
179 4 64 mmcblk0p4 dbi
179 5 512 mmcblk0p5 aboot
179 6 512 mmcblk0p6 rpm
179 7 512 mmcblk0p7 tz
179 8 512 mmcblk0p8 alt_sbl1
179 9 256 mmcblk0p9 alt_s1sbl
179 10 64 mmcblk0p10 alt_dbi
179 11 512 mmcblk0p11 alt_aboot
179 12 512 mmcblk0p12 alt_rpm
179 13 512 mmcblk0p13 alt_tz
179 14 20480 mmcblk0p14 boot
179 15 10240 mmcblk0p15 ramdump
179 16 16384 mmcblk0p16 FOTAKernel
179 17 32 mmcblk0p17 DDR
179 18 16384 mmcblk0p18 lta-label
179 19 1536 mmcblk0p19 modemst1
179 20 1536 mmcblk0p20 modemst2
179 21 1536 mmcblk0p21 fsg
179 22 8192 mmcblk0p22 apps_log
179 23 2379776 mmcblk0p23 system
179 24 204800 mmcblk0p24 cache
179 25 12589039 mmcblk0p25 userdata
179 32 4096 mmcblk0rpmb
1 block == 1 kByte == 1024 Bytes
--> get actual size in Byte: #blocks*1024 Bytes
How to install
unlock bootloader
fastboot flash FOTAKernel recovery.img (this should work in any case)
OR
fastboot flash recovery recovery.img (if my findings are correct, this should only work with new bootloader from here: https://forum.xda-developers.com/showpost.php?p=73575131&postcount=130 )
remove USB cable
press and hold Vol. down and power, if device vibrates release power and keep Vol. down holding. That's it.
Feel free to test and give comments on my thougts. :silly:
Credits:
SpritCroc (and AICP team)
munjeni (new bootloader)
Micha-Btz
charles1018
Sources:
my manifest: https://github.com/115ek/manifest
forked device tree: https://github.com/115ek/device_sony_amami
original device tree and kernel sources: https://github.com/aicp
TWRP: https://github.com/omnirom/android_bootable_recovery
One thing I forgot:
The recovery.img is packed into a .zip file. Please unpack first - it's not flashable via recovery.
I saw threads with a download section. Is this only possible with devDB threads?
Flashed, booted up fine.
Seems to be working okay
USB-OTG Not working for me.
roland080 said:
USB-OTG Not working for me.
Click to expand...
Click to collapse
Well, for me it worked without problems.
What isn't working in detail? What filesystem does your OTG device uses? What exactly did you do to mount and check for the files on the USB drive?
115ek said:
Well, for me it worked without problems.
What isn't working in detail? What filesystem does your OTG device uses? What exactly did you do to mount and check for the files on the USB drive?
Click to expand...
Click to collapse
My Pendrive is formatted as NTFS. A click on Select Storage and USB OTG "says" 0MB. The Pendrive is works fine in TWRP 3.1.1.
roland080 said:
My Pendrive is formatted as NTFS. A click on Select Storage and USB OTG "says" 0MB. The Pendrive is works fine in TWRP 3.1.1.
Click to expand...
Click to collapse
Hmm. Okay. I think I didn't include ntfs support. I'll have a look on this next build.
But did you set the check mark at USB OTG under mount menu point?
Do you also have an USB drive with fat format to test?
Thanks for the info
115ek said:
Hmm. Okay. I think I didn't include ntfs support. I'll have a look on this next build.
But did you set the check mark at USB OTG under mount menu point?
Do you also have an USB drive with fat format to test?
Thanks for the info
Click to expand...
Click to collapse
Yes, I do. Formatted as FAT32 but still not working.
Edit: Clicked on the Circle, but nothing happened.
I can only boot into TWRP by shutting down the phone and use vol- and power on at the same time, using the reboot to recovery option and adb reboot recovery command doesnt work. Is there any workaround for this? Previously I recall booting into 2 different twrp version by hardware buttons/software command that way
pipyakas said:
I can only boot into TWRP by shutting down the phone and use vol- and power on at the same time, using the reboot to recovery option and adb reboot recovery command doesnt work. Is there any workaround for this? Previously I recall booting into 2 different twrp version by hardware buttons/software command that way
Click to expand...
Click to collapse
you can always upgrade to a new TWRP inside TWRP itself! You can flash a new img file within twrp. You need to change the filter from zip to img though.
jho55 said:
you can always upgrade to a new TWRP inside TWRP itself! You can flash a new img file within twrp. You need to change the filter from zip to img though.
Click to expand...
Click to collapse
I'm already on the latest version of TWRP given in this post - although it was through flashing in TWRP 2.8.7.0 included in a pre-rooted stock rom. I'm just not being able to boot into twrp from the rom itself - only via hardware buttons
pipyakas said:
I can only boot into TWRP by shutting down the phone and use vol- and power on at the same time, using the reboot to recovery option and adb reboot recovery command doesnt work. Is there any workaround for this? Previously I recall booting into 2 different twrp version by hardware buttons/software command that way
Click to expand...
Click to collapse
The recovery you enter while holding Vol- and power is the one stored on FOTAKernel partition (that is the "real" one, it has got own kernel and ramdisk).
The recovery you enter with power and then Vol+ when LED lights up is the combined one. It is stored inside the boot partition.
The normal case is: kernel stored in boot.img starts and checks for user input. If you do so, a special recovery ramdisk gets loaded. Otherwise the "normal" ramdisk is loaded up.
Entering the recovery from inside the android system is a problem of your ROM. The system has to set a flag that survives reboot. Then the bootloader examines this flag and does the according operation.
roland080 said:
Yes, I do. Formatted as FAT32 but still not working.
Edit: Clicked on the Circle, but nothing happened.
Click to expand...
Click to collapse
There is still one thing you can test: enable/disable MTP. You can find this option under the mount menu point, too
115ek said:
There is still one thing you can test: enable/disable MTP. You can find this option under the mount menu point, too
Click to expand...
Click to collapse
Thank you! Now working with FAT32 Pendrive.
roland080 said:
Thank you! Now working with FAT32 Pendrive.
Click to expand...
Click to collapse
Cool
Can you test with ntfs, too? Only if that doesn't create circumstances
115ek said:
The recovery you enter while holding Vol- and power is the one stored on FOTAKernel partition (that is the "real" one, it has got own kernel and ramdisk).
The recovery you enter with power and then Vol+ when LED lights up is the combined one. It is stored inside the boot partition.
The normal case is: kernel stored in boot.img starts and checks for user input. If you do so, a special recovery ramdisk gets loaded. Otherwise the "normal" ramdisk is loaded up.
Entering the recovery from inside the android system is a problem of your ROM. The system has to set a flag that survives reboot. Then the bootloader examines this flag and does the according operation.
Click to expand...
Click to collapse
Well then that "flag" surely can trigger something, because I do remember booting into a different twrp version from within the rom than the "real" one. Also, the one booted from the rom always seem to have much worse brightness, if that's saying something. I cant exactly repeat the process to get that recovery either
115ek said:
Cool
Can you test with ntfs, too? Only if that doesn't create circumstances
Click to expand...
Click to collapse
No problem with FAT32! Works fine.
Edit: Sorry I tested with TWRP 3.1.0 :C I need to flash TWRP 3.2.1
Edit 2 Flashed TWRP 3.2.1, clicked on Mount, Enable MTP, then clicked on USB OTG but nothing happened. Still not works with FAT32.
pipyakas said:
Well then that "flag" surely can trigger something, because I do remember booting into a different twrp version from within the rom than the "real" one. Also, the one booted from the rom always seem to have much worse brightness, if that's saying something. I cant exactly repeat the process to get that recovery either
Click to expand...
Click to collapse
Yes, that sounds like your reboot-to-recovery option boots to the recovery included in boot.img, which came along with the installation of your ROM.
At the end a system call passes a "recovery" argument to the kernel restart function. This restart function then sets the kernel start parameters to the recovery-ramdisk and restarts the kernel (warm reboot).
If you want to enter the "real" recovery you have to explain the bootloader that he should load the kernel from FOTAKernel partition instead of boot partition.
You can google for more details, but there's not so much info unfortunately
https://stackoverflow.com/questions/5472761/how-does-the-bootloader-pick-up-the-command-after-a-restarting-system-with-comm
Nevertheless I'll look into it - it's really interesting. Another thing that's on my list is decryption support for TWRP...
roland080 said:
No problem with FAT32! Works fine.
Edit: Sorry I tested with TWRP 3.1.0 :C I need to flash TWRP 3.2.1
Edit 2 Flashed TWRP 3.2.1, clicked on Mount, Enable MTP, then clicked on USB OTG but nothing happened. Still not works with FAT32.
Click to expand...
Click to collapse
Try to disable MTP
115ek said:
Try to disable MTP
Click to expand...
Click to collapse
Not working. Hope you fix that later.
Related
I'm trying to do a factory restore of my gtab removing Clockworkmod and restoring it back to it's original out of box state (I'm not returning it, just want it back to stock for the moment). I downloaded nvflash, the drivers and the nvflash gtablet image and got it all setup. I run the batch file, everything goes through as it should, no errors. Yet when it finishes and the device reboots I still see it connecting to a wifi I had it connected to before (yet running TnT stock) and Clockworkmod is still on the device.
How exactly do I go about returning the tablet to stock if the nvflash isn't going to?
bekit's nvflash image from early November? I am pretty sure he had standard recovery in there, as I always had to replace it when I used it.
roebeet said:
bekit's nvflash image from early November? I am pretty sure he had standard recovery in there, as I always had to replace it when I used it.
Click to expand...
Click to collapse
I followed the instructions from this thread, by you So whatever you were saying to get, I got.
http://forum.xda-developers.com/showthread.php?t=861950
User data is retained with that setup - it's the only thing retained.
But I'm surprised that clockworkmod was still there. I had used this all the time and I always had standard recovery, afterwards. I actually had to re-run the nvflash later on to add clockworkmod. "part9.img" is the recovery partition - maybe bekit added cm later on that, and I have an old image.
roebeet said:
User data is retained with that setup - it's the only thing retained.
But I'm surprised that clockworkmod was still there. I had used this all the time and I always had standard recovery, afterwards. I actually had to re-run the nvflash later on to add clockworkmod. "part9.img" is the recovery partition - maybe bekit added cm later on that, and I have an old image.
Click to expand...
Click to collapse
Here is the output from the nvflash, let me know if something looks off. Not to mention I still have Superuser listed as an installed app. ><
How do I go about a FULL reset of this thing?
Code:
C:\nvflash>"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0270308342a0d397
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33554432/33554432 bytes sent
part8.img sent successfully
sending file: part9.img
/ 16777216/16777216 bytes sent
part9.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
\ 117292032/117292032 bytes sent
system.img sent successfully
Press enter to continue:
Your log looks correct to me (I've ran several restores on two different gtabs over the past few days). The only thing I wonder is if you got the right image(s) to begin with. I'm using bekit's restores from early November and not the ones with the "46" in the name (those are from later November).
part9.img is recovery. If you grab a recovery.img from stock and replace part9.img with that, you should have stock recovery after flashing.
User data is just a post-flash user data wipe and you are done.
markgolly said:
Your log looks correct to me (I've ran several restores on two different gtabs over the past few days). The only thing I wonder is if you got the right image(s) to begin with. I'm using bekit's restores from early November and not the ones with the "46" in the name (those are from later November).
Click to expand...
Click to collapse
Yea the one I got is named nvflash_gtablet_2010110500.zip, didn't grab the one with 46 in the name.
Seems you are doing everything right. I dunno - my restore has worked every time.
Anyway, I've got one of my gtabs in a boot-loop right now, so I need to do another restore (not using clockwork yet - one step at a time... ). I'll do the restore and repost once I am through it.
Oh, one last thing - I think bekit put Superuser on before he ran off the images. When I do my restore, it already has Superuser, too.
Well, chalk that up to a learning experience - seems I can't get out of a boot-loop via a TnT restore. Time to actually put cwm on....
markgolly said:
Oh, one last thing - I think bekit put Superuser on before he ran off the images. When I do my restore, it already has Superuser, too.
Click to expand...
Click to collapse
That would make sense then =)
i used update-smb_a1002-3053-user.zip flashed with cwm.
after reboot i restored the device from the system menu. it reflashed the original recovery and i don't see su anywhere.
That's exactly what I was gonna suggest!
madsquabbles said:
i used update-smb_a1002-3053-user.zip flashed with cwm.
after reboot i restored the device from the system menu. it reflashed the original recovery and i don't see su anywhere.
Click to expand...
Click to collapse
Sounds good, thanks a ton for the help guys.
So is anyone aware of what this update Viewsonic keeps talking about on Twitter is going to be?
Check out my post in the Developmet Section called "From Viewsonic"
madsquabbles said:
i used update-smb_a1002-3053-user.zip flashed with cwm.
after reboot i restored the device from the system menu. it reflashed the original recovery and i don't see su anywhere.
Click to expand...
Click to collapse
Stupid question, but what do you mean you restored from the system menu?
Can't see the micro SD card in my desktop
I inserted a 16GB SD card and is acknowledged in the tablet' storage, but once I connect the tablet with my desktop, the tablet shows as a removable disk with
13 GB. Why ???
I'm trying to install TNT_Lite and Flash.After downloading ClockworkMod I couldn't unzip the file to the microsd card because the SD card was not visible and couldn't locate it.
Can the "DiskCacheIndex1234.temp files be safely deleted?
markgolly said:
Seems you are doing everything right. I dunno - my restore has worked every time.
Anyway, I've got one of my gtabs in a boot-loop right now, so I need to do another restore (not using clockwork yet - one step at a time... ). I'll do the restore and repost once I am through it.
Oh, one last thing - I think bekit put Superuser on before he ran off the images. When I do my restore, it already has Superuser, too.
Click to expand...
Click to collapse
Hi,
Sorry to jump in, but what is "SuperUser'? I notice it's on my Gtab. Does it get installed as part of z4root?
Thx,
Jim
StirCwazy said:
Stupid question, but what do you mean you restored from the system menu?
Click to expand...
Click to collapse
if you go to settings, security, and do a factory data reset. this will wipe everything and restore the original recovery.
madsquabbles said:
if you go to settings, security, and do a factory data reset. this will wipe everything and restore the original recovery.
Click to expand...
Click to collapse
OK sorry, I know that one just didn't know if you were talking about that or something else I wasn't familiar with on the gtab.
EDIT: These links are no longer available because some people copy these links to forums with "questionable" contents and some company scrape links from those forums and DMCA them all without actually checking them first. Please use the official CWM from now on. Download the official version at http://www.clockworkmod.com/rommanager.
This image is built via unofficial CM10 source linked here
Download
Recovery image: http://www.mediafire.com/?w707lr78by1bbd6 (MD5: 34a2caff881dfa7faf941cb1d34ec3b8)
Recovery image (touch): http://www.mediafire.com/?ff304ho7h9pbapg (MD5: f9aab0807bb5350c5b69d795906fecb5)
Use fastboot to flash
Code:
fastboot flash recovery recovery-a700-6015.img
Enter recovery via vol down + power or
Code:
adb reboot recovery
Old Download
6.0.14
Recovery image: http://www.mediafire.com/?9g39c74cc1smq10 (MD5: b2688a47f5a754e5374df4f2abd3b445)
Recovery image (touch): http://www.mediafire.com/?gtfmvb6on1ivgrq (MD5: 534f7d73d5a77fcec6ab2c21a8a48a71)
6.0.11 Update 1: http://www.mediafire.com/?o5skj3acsatq633 (MD5: 52b61d78940101d72eab20689d47f2ba)
Congratulations, it unfortunately can not test because I have an A510. Is the recovery from a510/a700 the same? Actually, the tablets are different only in the display, right? Has anybody tried to flash a recovery from an a700 to a A510? Where did you get the two files, especially the fstab?
Thanks!
Thanks, have you fully tested it ? We've had a couple of recos that managed to bricked tablets so far
Edit : you have not tested the wipe ? Those one bricked my A700 so be careful.
Rembold91 said:
Congratulations, it unfortunately can not test because I have an A510. Is the recovery from a510/a700 the same? Actually, the tablets are different only in the display, right? Has anybody tried to flash a recovery from an a700 to a A510? Where did you get the two files, especially the fstab?
Thanks!
Click to expand...
Click to collapse
The boot.img was dumped from my device using dd, recovery.fstab was based on Nexus 7's and modified to suit our device. I'm not sure about the A510 since I don't have one.
paugustin said:
Thanks, have you fully tested it ? We've had a couple of recos that managed to bricked tablets so far
Edit : you have not tested the wipe ? Those one bricked my A700 so be careful.
Click to expand...
Click to collapse
Wipe works both from system and recovery itself.
OK thanks for the info.
Too bad my tablet is still unable to boot
paugustin said:
OK thanks for the info.
Too bad my tablet is still unable to boot
Click to expand...
Click to collapse
Are you able to boot into fastboot? Are you able to boot into recovery using the orientation lock + volume down + power?
EDIT: Oh wait, this device has no way of booting into fastboot without a working system?
pawitp said:
Are you able to boot into fastboot? Are you able to boot into recovery using the orientation lock + volume down + power?
Click to expand...
Click to collapse
Yes fastboot and recovery mode are available. I can flash rom but they won't boot and whenever I use wipe/format on a partition the process will freeze.
paugustin said:
Yes fastboot and recovery mode are available. I can flash rom but they won't boot and whenever I use wipe/format on a partition the process will freeze.
Click to expand...
Click to collapse
Hmm, can you add me on GTalk [email protected]?
Just checking procedure please....
I got the OTA update today to Image version: Acer_AV043_A700_RV07RC06_PA_CUS1 Build: Acer_AV043_A700_1.029.00_PA_CUS1
I had to unlock the bootloader and root again. ***OTA Rootkeeper WILL NOT keep the root! The bootloader is re-written and root removed***
I just downloaded the Recovery.img file and want to be SURE I do this correctly, so please forgive me if I sound "noobish"!
1. Copy Recovery.img to root of SD Card
2. Use ADB Fastboot to get tablet into flashboot mode
3. Once tablet has entered flashboot, Type -fastboot flash recovery recovery.img
4. Process should allow me to enter Recovery mode
Am I correct here? I don't want to brick my tab! I appreciate any input and thanks in advance!
paugustin said:
OK thanks for the info.
Too bad my tablet is still unable to boot
Click to expand...
Click to collapse
Have you tried using nvflash in apx mode ?
Well we don't have a fully working nvflash for tegra 3 with sbk support yet. If you have one I'm interested
Sent from my S300 using xda app-developers app
paugustin said:
Well we don't have a fully working nvflash for tegra 3 with sbk support yet. If you have one I'm interested
Sent from my S300 using xda app-developers app
Click to expand...
Click to collapse
Did you check the a700 service rom? It seems it has the NVFlash support as near as I can tell. Should be the same for the 701. Looks like it has support for the blocks.
I can't do anything with it. Tab is still in for repair. Hope maybe this week,
MD
pawitp said:
Wipe works both from system and recovery itself.
Click to expand...
Click to collapse
Sounds good. However, let me be a little more specific.
The problem with all the previous recoveries happened when you tried to wipe /Data. All the other functions seemed to work well. Seemed to.
1. Recovery backup took longer than usual, especially on a bare stock install.
2. The first time you restore a recovery image, it would take "forever". Usually, it would complete the first time, but Data apps didn't function once the Rom booted. Nor could you download ANY apps. Any additional attempts to do a restore would hang at "formatting data". Once that happened, you basically could not install anything nor restore from a recovery. /Data corrupted.
So the question again, have you tested the /data wipes and formats via CWM? Several times after downloading apps, backups, restores?
Please don't take this the wrong way. We appreciate taking the time developing a workable recovery for the 70x. But the previous attempts caused needless bricked tabs. 1 dev, didn't even own a 70x to test it on and he pushed it out. And the other guy, well, whereabouts unknown, and knowing the previous issues, he also never bothered to check all functions before releasing his version. Claimed "I don't have a need to wipe data".
So please clear this issue, before we get into the flashing portion. You have to understand, some of us, are a little "gun-shy" right now.
Thanks for taking the time to develop a recovery! I hope it works well!
MD
paugustin said:
Well we don't have a fully working nvflash for tegra 3 with sbk support yet. If you have one I'm interested
Sent from my S300 using xda app-developers app
Click to expand...
Click to collapse
I'll take a guess, that if the /data issue is working in the new recovery, and you can get it installed, you may be able to wipe the corrupted /data, and restore your previous recovery backup. If you used a CWM based recovery.
Also, I think I may still have my stock recovery CWM backup from my 701 on my PC (build .015) (I think). But considering it was done with CWM, you may be able to restore it. Might work, might not.
MD
OK I spent some time this morning with pawitp. He was able to make my A700 boot but the /data partition is reduced to 126Meg and if I try to format any partition it will break things again.
So it's a start...
Regarding restore, I have a CWM backup of my system but so far my attempts at restoring it have failed, even with pawitp recovery. The partition is broken so it won't take any data.
paugustin said:
OK I spent some time this morning with pawitp. He was able to make my A700 boot but the /data partition is reduced to 126Meg and if I try to format any partition it will break things again.
So it's a start...
Regarding restore, I have a CWM backup of my system but so far my attempts at restoring it have failed, even with pawitp recovery. The partition is broken so it won't take any data.
Click to expand...
Click to collapse
Well, that's a bit of good news. Similar to the SGS II and their leaked kernel. They had to flash a modified PIT that ignored the corrupted sectors. Lost 2gb in the process, but still a start.
MD
Partitions on the A700
Just to shed some light on the partitions of our new toy.
Maybe it's of use as a reference.
Block devices:
/ # ls -l /dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx root root 2012-07-24 10:28 AKB -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-07-24 10:28 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-07-24 10:28 CAC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-07-24 10:28 DE2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-07-24 10:28 FLX -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-07-24 10:28 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-07-24 10:28 MSC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-07-24 10:28 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-07-24 10:28 UDA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-07-24 10:28 USP -> /dev/block/mmcblk0p8
Partition sizes:
/ # cat /proc/partitions
major minor #blocks name
179 0 31260672 mmcblk0
179 1 6144 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 614400 mmcblk0p3
179 4 1253376 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 102400 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 20480 mmcblk0p8
179 9 10240 mmcblk0p9
179 10 29204480 mmcblk0p10
179 32 15558144 mmcblk1
179 33 15558136 mmcblk1p1
Moscow Desire said:
Sounds good. However, let me be a little more specific.
The problem with all the previous recoveries happened when you tried to wipe /Data. All the other functions seemed to work well. Seemed to.
1. Recovery backup took longer than usual, especially on a bare stock install.
2. The first time you restore a recovery image, it would take "forever". Usually, it would complete the first time, but Data apps didn't function once the Rom booted. Nor could you download ANY apps. Any additional attempts to do a restore would hang at "formatting data". Once that happened, you basically could not install anything nor restore from a recovery. /Data corrupted.
So the question again, have you tested the /data wipes and formats via CWM? Several times after downloading apps, backups, restores?
Please don't take this the wrong way. We appreciate taking the time developing a workable recovery for the 70x. But the previous attempts caused needless bricked tabs. 1 dev, didn't even own a 70x to test it on and he pushed it out. And the other guy, well, whereabouts unknown, and knowing the previous issues, he also never bothered to check all functions before releasing his version. Claimed "I don't have a need to wipe data".
So please clear this issue, before we get into the flashing portion. You have to understand, some of us, are a little "gun-shy" right now.
Thanks for taking the time to develop a recovery! I hope it works well!
MD
Click to expand...
Click to collapse
Don't worry, the data partition is never actually formatted because the internal sdcard lies in /data/media. All the recovery does is delete all the files not in /data/media.
Sent from my A700 using xda app-developers app
pawitp said:
Don't worry, the data partition is never actually formatted because the internal sdcard lies in /data/media. All the recovery does is delete all the files not in /data/media.
Sent from my A700 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I meant User Data/Factory Reset (as CWM calls it).
This is why when on the first attempt at restoring a recovery, the downloaded apps would not function. You had the icons, but Force Close on them all. The system apps were fine. Any attempt to restore any previous backup failed (would hang on that partition). Couldn't wipe the partition in CWM after that.
MD
Moscow Desire said:
Sorry, I meant User Data/Factory Reset (as CWM calls it).
This is why when on the first attempt at restoring a recovery, the downloaded apps would not function. You had the icons, but Force Close on them all. The system apps were fine. Any attempt to restore any previous backup failed (would hang on that partition). Couldn't wipe the partition in CWM after that.
MD
Click to expand...
Click to collapse
And that basically clears data. I've tested it, it works (and mentioned it on first page).
I recentlly attempted to update my P6800 from ICS LQ1 to LQ2 via Mobile Odin.
The result was a tablet that would only boot as far as the Samsung Logo and boot chime and would hang there.
Many attempts were made to clear caches, reset data via both stock recovery and CWM versions 5 .5 and even 6 with no change.
Tried using PC Odin to go back to LQ1 and has the same exact results. suspected an error in a partition and used a stock p6800 .pit along with stock LQ1 .tar and still have same problem. Cm9 and 10 gives same results.
However I am able to install stock Honeycomb via PC Odin which seems to work fine except CWM backup is unable to restore a backup and hangs just after starting.
I still suspect a bad partition somewhe but dont see a way of verifying this. Have read many posts both here and in the Galaxy Note forum but none have solution that has worked for me.
Does anyone know if the .pit file actually recreates your partitions? Or does someone have instructions on how I can manually do this via adb shell? Specifically the cache, data and system partitins.
Any help is appreciated.
Try this.
- In HC use Locerra' CWM v5.x
In recovery:
- Clear cache.
- Dalvik.
- Data reset.
- Flash rom: http://www.androidtablets.net/forum/showthread.php?p=223379
- Fix permission.
- Reboot.
If stuck after reboot...boot to cwm recovery again.
- Full wipe.
- Reboot and wait a while.
Hope it help and keep us posted
Astrix Ashburn said:
Try this.
- In HC use Locerra' CWM v5.x
In recovery:
- Clear cache.
- Dalvik.
- Data reset.
- Flash rom: http://www.androidtablets.net/forum/showthread.php?p=223379
- Fix permission.
- Reboot.
If stuck after reboot...boot to cwm recovery again.
- Full wipe.
- Reboot and wait a while.
Hope it help and keep us posted
Click to expand...
Click to collapse
followed above and got non stop rebooting.
wonder if ics uses a different partition structure.
While at recovery do u have testbend?
Sent from my GT-P6800 using xda premium
I faced your situation before, here's what you should do
1 Install official HC 3.2 using PC odin
2 boot in to HC stock recovery
3 factory reset / Data & Cache wipe
4 do full boot into HC till you see your desktop
5 use your PC odin or Mobile odin pro to Install ICS over HC
6 Now you should be good to go.
Note if you can successfully boot into HC then your paritions are good, dont mess with them.
zorbakun said:
I faced your situation before, here's what you should do
1 Install official HC 3.2 using PC odin
2 boot in to HC stock recovery
3 factory reset / Data & Cache wipe
4 do full boot into HC till you see your desktop
5 use your PC odin or Mobile odin pro to Install ICS over HC
6 Now you should be good to go.
Note if you can successfully boot into HC then your paritions are good, dont mess with them.
Click to expand...
Click to collapse
This has been tried several times with the same results each time. Boot loops.
Thats what I don't get, HC works but as soon as ICS is put on I get /Data partition errors. More specifically /data cannot be mounted.
Josvaz said:
While at recovery do u have testbend?
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Yes , in stock recovery I do. Was not sure what that did.
Looking at my partitions via adb it looks like /dev/block/mmcblk0p10 is empty. Perhaps this is the issue? If so, does anyone know how to recreate?
~ # parted /dev/block/mmcblk0p10
parted /dev/block/mmcblk0p10
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p10
Welcome to GNU Parted! Type 'help' to view a list of co
(parted) print
print
print
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted) print list
print list
print list
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted)
kable said:
Looking at my partitions via adb it looks like /dev/block/mmcblk0p10 is empty. Perhaps this is the issue? If so, does anyone know how to recreate?
~ # parted /dev/block/mmcblk0p10
parted /dev/block/mmcblk0p10
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p10
Welcome to GNU Parted! Type 'help' to view a list of co
(parted) print
print
print
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted) print list
print list
print list
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted)
Click to expand...
Click to collapse
its look like the /data partition is screwed... try running e2fsck -fDC0 /dev/block/mmcblk0p10 to check the partition...
this is the EXACT problem i was having. here's what i did to fix it*:
disclaimer: i am waiting for HC filefactory slow-*ss download to take another F*CKING hour.... so i have yet to FULLY recover my tab... BUT i think i'm onto something.
i COULD get a full flash from odin with no hanging up...then i corrupted my /data and /system partition... don't ask me how: i knew to stay away from wiping with 3e stock ICS recovery, i used cwm 5.8.1 temporary zip that i flashed from stock recovery, IT messed up everything.... then i started trying to follow androguide.fr's revive from superbrick guide. (will post link later)
after days and days and DAYS of frustration trying to remove and remake /data and /system, /cache eventually corrupted. i was ready to blow my brains out.... just on a whim, without having read any of this stuff, i:
1) flashed the original pit file,
2) flashed ATO-ICS firmware
3) flashed CWM 6.0.1.1
4) wiped /data /factory /dalvik SUCCESSFULLY!!!!
5)....after wiping, e2fsck checking and getting clean partitions with every ICS CM9/10 rom i could find, and STILL getting stuck on the boot animation...
i finally read in a gNote forum that people with this problem were flashing back to GB (original firmware for the Note) and solving their problem, then they could go back to ICS... if you can't i'm SORRY!!! but i'm even just trying to get ANYTHING to boot at this point. YOU'RE POST GIVES ME HOPE!!!!
so try: flashing the original pit file, flash cwm 6.0.1.1, wipe data/factory reset, wipe dalvik cache, reboot and JUST do the e2fsck section of the NOOB friendly guide to recovering your tab from superbrick. --will post link later. that should at LEAST get rid of the corrupt filesystem. e2fsck every partition that you were having trouble with.
zorbakun said:
I faced your situation before, here's what you should do
1 Install official HC 3.2 using PC odin
2 boot in to HC stock recovery
3 factory reset / Data & Cache wipe
4 do full boot into HC till you see your desktop
5 use your PC odin or Mobile odin pro to Install ICS over HC
6 Now you should be good to go.
Note if you can successfully boot into HC then your paritions are good, dont mess with them.
Click to expand...
Click to collapse
Thank you for this, it got me working again. I didnt think to do any wipes after going back to stock HC but it was exactly what it needed.
nutley said:
Thank you for this, it got me working again. I didnt think to do any wipes after going back to stock HC but it was exactly what it needed.
Click to expand...
Click to collapse
You should change your topic by adding ( Resolved ) to it so others know you got it figured out .
Fluxcore said:
You should change your topic by adding ( Resolved ) to it so others know you got it figured out .
Click to expand...
Click to collapse
It's not my topic. Just saying thanks as it sorted my own issue out
When I tried to boot into recovery it factory reset instead. Please help I switch back to the stock recovery but it still won't boot it still factory reset the phone
I'm using Canvas 2 A110 running on CanvaS4 custom rom
Hey, i faced same problem then i downloaded stock rom v2 from below link and flash it through sp flash tool and then flashed the CWM recovery 6.0.2 successfuly by mobile uncle mtk tools.
Finally i got my CWM recovery.
Link:- http://www.4shared.com/rar/ARs-Ctye/Micromax_A110.html
This is containing both stock rom V1 and V2.
Hit the thanks button if this help you.
MR.COLOURFULL said:
Hey, i faced same problem then i downloaded stock rom v2 from below link and flash it through sp flash tool and then flashed the CWM recovery 6.0.2 successfuly by mobile uncle mtk tools.
Finally i got my CWM recovery.
Link:- http://www.4shared.com/rar/ARs-Ctye/Micromax_A110.html
This is containing both stock rom V1 and V2.
Hit the thanks button if this help you.
Click to expand...
Click to collapse
its not resolving the solution ....
same problem for me its factory rest when reeboing into recovery mode ,.................................
any other perfect solution .....?????
Solved
Sent from my A110 using xda premium
Same problem bro Plz help
Ravinath said:
Same problem bro Plz help
Click to expand...
Click to collapse
So follow the above method
Same problem is with me... Plz help me.. I don't have my lappy ryt now... Plz tell me how can I solve this prob. With my phone... Thanks in advance
having issue with canvas 2
i have installed one of the custom roms from the xda forum and its not working ..so i wish to install my stock rom but when i go to recovery mod it goes in to resets instead of going in to recovery mod ...help me please
problem
Same happened with mine also..stuck up followed the above procedure ..still phone hang
nadeems007 said:
Same happened with mine also..stuck up followed the above procedure ..still phone hang
Click to expand...
Click to collapse
install stock recovery again using mobileuncle tools and then download ctr touch recovery and install it through mobileuncle tools
how to root micromax A110 with note 3 interface installed
i have created a great mess,1st i rooted my phone (micromax a110) and then i installed LegoIce™_Fusion_v3 custom rom.Then i forgot to install playstore so i tired to do it using cwm bt it didn't work. Then eventually my phone stopped going in the recovery mode and i unrooted my phone. Now the problem is that when i try to root my phone using binary it doesn't work.I'm stuck with note 3 interface and google apps don't work PLEASE HELP!!!!!!
pranil546 said:
i have created a great mess,1st i rooted my phone (micromax a110) and then i installed LegoIce™_Fusion_v3 custom rom.Then i forgot to install playstore so i tired to do it using cwm bt it didn't work. Then eventually my phone stopped going in the recovery mode and i unrooted my phone. Now the problem is that when i try to root my phone using binary it doesn't work.I'm stuck with note 3 interface and google apps don't work PLEASE HELP!!!!!!
Click to expand...
Click to collapse
install stock rom (jelly bean/ICS) through flash tools and then root it again by the following the correct method for ICS or jelly bean.
bonafide124 said:
i have installed one of the custom roms from the xda forum and its not working ..so i wish to install my stock rom but when i go to recovery mod it goes in to resets instead of going in to recovery mod ...help me please
Click to expand...
Click to collapse
You might be using wrong kernel. Which ROM and kernel did you flashed?
rebooting by itself, cant go into the recovery mode, couldnt do anything
bro
i rooted my canvas 2
curently on lewa os
everything was fine until i once did factory reset
and the result is my phone getting restarted by itself
all i can see now is the boot image followed by the android logo with a rotating tesseract kind of thing in its belly and a progress bar in the bottom
and once again the boot image ..
restarting again n again
repeatedly
unable to get into the recovery mode too
its out of control
pls suggest me how i can come over the problem
coppers said:
bro
i rooted my canvas 2
curently on lewa os
everything was fine until i once did factory reset
and the result is my phone getting restarted by itself
all i can see now is the boot image followed by the android logo with a rotating tesseract kind of thing in its belly and a progress bar in the bottom
and once again the boot image ..
restarting again n again
repeatedly
unable to get into the recovery mode too
its out of control
pls suggest me how i can come over the problem
Click to expand...
Click to collapse
You need to flash stock ROM with sp flash tool....
I had faced the same issue as you....I just flashed stock ROM with sp and everything became normal....
happy to see more people like me
coppers said:
l i can see now is the boot image followed by the android logo with a rotating tesseract kind of thing in its belly and a progress bar in the bottom
and once again the boot image ..
restarting again n again
repeatedly
unable to get into the recovery mode too
its out of control
Click to expand...
Click to collapse
sorry , but i cant help laughing
its funny the way you describe it...
im dealing with the exact same problem for over a month now..
sp tools wont detect my phone..
gave up on it , now im plannin to buy a moto e or g or something
this was the log i found in "/cache/recovery/last_log"
Starting recovery on Sat Dec 27 16:04:00 2014
framebuffer: fd 4 (480 x 854)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM-based Recovery v6.0.1.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/bootimg (null) 0
2 /cache ext4 /dev/block/mmcblk0p4 (null) 0
3 /data ext4 /dev/block/mmcblk0p5 (null) 0
4 /misc emmc /dev/misc (null) 0
5 /recovery emmc /dev/recovery (null) 0
6 /emmc vfat /dev/block/mmcblk0p6 (null) 0
7 /system ext4 /dev/block/mmcblk0p3 (null) 0
8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Boot command: boot-recovery
I:Got arguments from boot message
I:Checking arguments.
unknown option -- locale=en_IN
E:Invalid command argument
I:device_recovery_start()
Command: "recovery" "--wipe_data" "--locale=en_IN"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
persist.service.acm.enable=0
ro.product.model=ZTE V970
ro.product.brand=ZTE
ro.product.name=P175A20
ro.product.device=P175A20
ro.product.board=ztenj77_cu_ics
ro.product.manufacturer=ZTE
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6577
ro.revision=1710983680
ro.emmc=0
sys.usb.vid=19D2
init.svc.recovery=running
init.svc.adbd=restarting
sys.usb.config=mass_storage,adb
service.adb.root=1
sys.usb.state=mass_storage,adb
Formatting /data...
Creating filesystem with parameters:
Size: 1610612736
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 6144
Label:
Blocks: 393216
Block groups: 12
Reserved block group size: 95
Created filesystem with 11/98304 inodes and 12897/393216 blocks
Formatting /cache...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
Click to expand...
Click to collapse
any devs pls check this out and tell us what went wrong
hi,
previously i did this cwm successfully.
but now am not able to boot into recovery mode. instead its factory reseting.
when pressing up+down+power buton its showing 1.recover 2. factory mode.
if i select 1. ,it will factory reset no wipe or any other option is there,
Any help ???
robotux said:
hi,
previously i did this cwm successfully.
but now am not able to boot into recovery mode. instead its factory reseting.
when pressing up+down+power buton its showing 1.recover 2. factory mode.
if i select 1. ,it will factory reset no wipe or any other option is there,
Any help ???
Click to expand...
Click to collapse
i was facing the same issue earlier. I tried so many things like try to install CWM with mobile uncle tool. and also try to flash only CWM file through SPtool but fails.
But when i flash whole stock rom through SPtool it worked and now there is no problem at all
i suggest you to flash stock rom wia SPtool and flash CWM as well
all the best.............
I want to increase size of recovery partition on Lenovo K30W so I can flash larger recovery image created for Lenovo A6000. I have devised a way, but I would be grateful if someone could look it over and spot possible flaws.
Here is the current partition table.
Code:
Model: MMC Q8XSAB (sd/mmc)
Disk /dev/block/mmcblk0: 15634268160B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67108864B 134217727B 67108864B fat16 modem
2 134217728B 134742015B 524288B sbl1
3 134742016B 135266303B 524288B sbl1bak
4 135266304B 136314879B 1048576B aboot
5 136314880B 137363455B 1048576B abootbak
6 137363456B 137887743B 524288B rpm
7 137887744B 138412031B 524288B rpmbak
8 138412032B 138936319B 524288B tz
9 138936320B 139460607B 524288B tzbak
10 139460608B 139984895B 524288B hyp
11 139984896B 140509183B 524288B hypbak
12 140509184B 141557759B 1048576B pad
13 141557760B 143130623B 1572864B modemst1
14 143130624B 144703487B 1572864B modemst2
15 144703488B 145752063B 1048576B misc
16 145752064B 145753087B 1024B fsc
17 145753088B 145761279B 8192B ssd
18 145761280B 156247039B 10485760B splash
19 201326592B 201359359B 32768B DDR
20 201359360B 202932223B 1572864B fsg
21 202932224B 202948607B 16384B sec
22 202948608B 219725823B 16777216B boot
23 219725824B 1830338559B 1610612736B ext4 system
24 1830338560B 1863892991B 33554432B ext4 persist
25 1863892992B 1998110719B 134217728B ext4 cache
26 1998110720B 2014887935B 16777216B recovery
27 2014887936B 15634251263B 13619363328B ext4 userdata
Luckily, recovery and data partition are next to each other. Here is the procedure, please tell me if it is viable.
1. Boot into recovery
2. Create nandroid backup of data partition
3. Make sure that data partition is unmounted in recovery
4. Using parted, delete recovery and data partitions, and then recreate them with new sizes
5. Format data partition
6. Make sure that "use rm -rf instead of formatting" is enabled in recovery settings
7. Restore nandroid backup
8. Flash new recovery
9. Reboot
These are the commands I would use:
Code:
adb shell
parted /dev/block/mmcblk0
unit b
rm 27
rm 26
mkpart primary 1998110720 2031665151
mkpart primary 2031665152 15634251263
name 26 recovery
name 27 userdata
quit
mke2fs -t ext4 /dev/block/mmcblk0p27
As there were no replies, I took a risk and went ahead with resizing the partitions. The described procedure worked without problems.
Could you make a guide on how you did this exactly for noobs?
I understand that you posted the steps you used, but i'm not familiar with what you did.
Also, what rom are you using currently?
I got a rom working for this phone, It works well, but is not ideal.
https://forum.xda-developers.com/general/help/k3-note-question-k30w-t3531158
addict1337 said:
Could you make a guide on how you did this exactly for noobs?
I understand that you posted the steps you used, but i'm not familiar with what you did.
Also, what rom are you using currently?
I got a rom working for this phone, It works well, but is not ideal.
https://forum.xda-developers.com/general/help/k3-note-question-k30w-t3531158
Click to expand...
Click to collapse
Well, making an even more detailed guide will take some effort. I'll do it when I find the time.
I am using this ROM: https://forum.xda-developers.com/lenovo-a6000/development/rom-resurrectionremix-5-8-1-t3555184
It's great, but I do have problems with updating it. Hopefully it'll be resolved soon.
Here is a more detailed procedure. However, if you are not familiar with Linux command line and the Android partition layout, I strongly recommend that you stay away from this.
First, you need Android platform tools from here. Download for your platform (I am going to assume Windows) and extract to a folder of your choosing (for example C:\Android).
You also need parted utility, download from here. It's best to extract it to the same folder as Android platform tools.
Next, open Windows command prompt and go to the platform tools folder. The easiest way to do it is to open the folder in Windows Explorer, right click in the empty space while holding shift and choose "Open command window here". Reboot your device in recovery mode and connect it to the computer USB port.
While in recovery, make a backup of your data partition.
Copy the new recovery image to external SD if you have one, or else to internal memory. You can do it using Windows Explorer.
Copy parted utility to the device.
Code:
adb push parted /.
Next, enter device shell.
Code:
adb shell
Make parted executable.
Code:
chmod a+x parted
Start parted utility.
Code:
./parted /dev/block/mmcblk0
Be extremely careful from now on. Every parted command is executed immediately, so if you type something wrong, you could brick your device.
Change size unit to byte.
Code:
unit b
Print your current partition layout. If it's not the same as in my original post, abort now as you'll mess things up.
Code:
p
Remove recovery and data partitions.
Code:
rm 27
rm 26
Recreate partitions with new sizes (recovery is now 32MB instead of previous 16MB).
Code:
mkpart primary 1998110720 2031665151
mkpart primary 2031665152 15634251263
Give partitions the same names as before.
Code:
name 26 recovery
name 27 userdata
Exit parted utility.
Code:
quit
Format the data partition.
Code:
mke2fs -t ext4 /dev/block/mmcblk0p27
Make sure that "use rm -rf instead of formatting" is enabled in recovery settings. This may not be necessary, but I've seen it in some tutorial, and it can't hurt.
Restore data partition from backup.
Flash new recovery using current recovery (go to install and choose "install image").
Reboot and hope for the best.
Thank you very much
I will give it a try.
All worked well, however I am never able to boot into recovery from my phone itself (before i attempted this, and after).
I always need to use my pc/usb to boot into recovery via a batch file.
Even if I install recovery from the recovery I just booted.
Getting into recovery is holding volume up and the power button right?
I installed the software you mentioned, however it is stuck at the bootscreen
addict1337 said:
All worked well, however I am never able to boot into recovery from my phone itself (before i attempted this, and after).
I always need to use my pc/usb to boot into recovery via a batch file.
Even if I install recovery from the recovery I just booted.
Getting into recovery is holding volume up and the power button right?
I installed the software you mentioned, however it is stuck at the bootscreen
Click to expand...
Click to collapse
To get into recovery, you need to keep BOTH up and down volume keys, and then power on. After a few seconds, you can release volume keys.
As far as the ROM is concerned, make sure you wipe data and cache before installing it. That's all I can think of.
CrazyNik said:
To get into recovery, you need to keep BOTH up and down volume keys, and then power on. After a few seconds, you can release volume keys.
As far as the ROM is concerned, make sure you wipe data and cache before installing it. That's all I can think of.
Click to expand...
Click to collapse
Thanks.
I managed to install a CWM recovery for A6000, witch is working fine now (32MB)
I had problems with GPS on my Cyanongenmod Rom modified for K30-W, but after installing gapps all is working fine now.
Thank you for your help!
I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.
addict1337 said:
I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.
Click to expand...
Click to collapse
You must use TWRP 3.1.0, but even with it, RR 20170403 will not install on K30W firmware, I don't know why. I managed to install it by flashing A6000 firmware first. I will post the tutorial on RR thread when I find the time.
addict1337 said:
I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.
Click to expand...
Click to collapse
I've posted the tutorial here.
CrazyNik said:
I've posted the tutorial here.
Click to expand...
Click to collapse
Awesome, I was waiting for it
Thank you very much.