Related
So, what is it.
Like, what I mean is when I use df it shows what is mounted, but only the mount points, not the devices.
Like ex. /dev/somestuff here is mounted to /data
or ex on my pc. /dev/sda2 is mounted to /
Specifically I want to know what is mounted to /data.
Thanks, sorry if my question is a bit unclear.
Code:
[email protected]:/ # ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
lrwxrwxrwx root root 2012-01-25 09:15 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-01-25 09:15 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-01-25 09:15 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-01-25 09:15 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-01-25 09:15 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-01-25 09:15 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-01-25 09:15 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-01-25 09:15 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-01-25 09:15 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-01-25 09:15 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-01-25 09:15 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-01-25 09:15 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-01-25 09:15 xloader -> /dev/block/mmcblk0p1
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Now: one common recovery for all: jflte
The jfltexx variant is no more updated, use jflte common variant
i9505 (jfltexx ---> jflte)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Big thanks to @wanam and @ausdim for their great support with providing kernels and support in compiling them
Nice to see you in SGS4 Forums Phil Keep your awesome work on
Where's my thanks?
Great to see you here. Download and flashed now.
Great
Waiting for first feedback to remove the scary red warning
Awesome PhilZ!
Someone please confirm this works fine!
Not Working by me. Black Screen in recovery. See only the Button on the bottom but the rest is black.
Edit: Ok working. Wait 1 Minute and the Screen is coming but the touch not working correct. The Hardware button also not correct working.
Yes Phil it's in the house!!!!
Can you give more details
Touch is completely dead or it behaves bad. In that case, how does it act (a video would be helpful)
What issue with hardware buttons
And is the black screen delay on each start
Phil3759 said:
Can you give more details
Touch is completely dead or it behaves bad. In that case, how does it act (a video would be helpful)
What issue with hardware buttons
And is the black screen delay on each start
Click to expand...
Click to collapse
Black Screen on each start yes. After 10 seconds i see the recovery. With the hardware buttons louder and quieter i can not select ever entry. Only every second i can select. With Touch nothing correct working. In Arome the bottom bottons not working. The Font are very small.
Sorry my English is not so good.
Same problems like Schrotty. After choosing something by touch, it seems the screen doesn't refresh. If I go up or down, the screen appears.
Also I tried to format /cache ... it says Done, but from that point I get the messages "Can't mount /cache/*" ... the problem all the recent recoverys had.
On the right top I see time ... it shows me 02:14 ... no wonder the recent recoveries couldn't have a correct time in backup for me. Strange why some users have correct time/date ....
@Phil3759,you need to modify graphics.c.
Chenglu said:
@Phil3759,you need to modify graphics.c.
Click to expand...
Click to collapse
Ah, thank you
However, without a cm source (I use common jflte) and a device to test (still only an i9100), i have no idea where to start to fix it
Phil3759 said:
Ah, thank you
However, without a cm source (I use common jflte) and a device to test (still only an i9100), i have no idea where to start to fix it
Click to expand...
Click to collapse
I send a PM to you.
Sir Phil, great to see you here!
One question : it is possible to include an autoroot option in your cwm, like it is in the Note recovery?
On S2 only flash your kernel, got cwm, got root, got everything together. Niw it us a little bit different. That's why i ask for the autoroot option.
Gesendet mit meinem S IV
Mr.AFK said:
Sir Phil, great to see you here!
One question : it is possible to include an autoroot option in your cwm, like it is in the Note recovery?
On S2 only flash your kernel, got cwm, got root, got everything together. Niw it us a little bit different. That's why i ask for the autoroot option.
Gesendet mit meinem S IV
Click to expand...
Click to collapse
On N7000 and I9100 the kernel and recovery were one .img.
Kernel contained recovery. Since S3 and up, recovery is a separate partition.
Code:
lrwxrwxrwx root root 1970-01-09 01:56 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-09 01:56 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-09 01:56 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-09 01:56 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-09 01:56 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-09 01:56 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-09 01:56 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-09 01:56 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-09 01:56 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-09 01:56 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-09 01:56 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-09 01:56 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-09 01:56 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-09 01:56 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-09 01:56 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-09 01:56 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-09 01:56 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-09 01:56 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-09 01:56 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-09 01:56 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-09 01:56 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-09 01:56 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-09 01:56 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-09 01:56 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-09 01:56 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-09 01:56 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-09 01:56 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-09 01:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-09 01:56 userdata -> /dev/block/mmcblk0p29
Mr.AFK said:
Sir Phil, great to see you here!
One question : it is possible to include an autoroot option in your cwm, like it is in the Note recovery?
On S2 only flash your kernel, got cwm, got root, got everything together. Niw it us a little bit different. That's why i ask for the autoroot option.
Gesendet mit meinem S IV
Click to expand...
Click to collapse
In new cwm 6.0.3.2, Koush added a function to prompt you to root on recovery restart if you loose root
It will copy su binary to where it should
After that, just install Koush CWM Superuser from market and you are rooted
Can I use this method initially?
So flash your recovery on stock rom, boot into it, "enable root procedure", boot up und go to play an install superuser app?
That's all?
Gesendet mit meinem S IV
Hey Phil, nice to see you here. Always used your recovery on my note2.
I also get the black screen, I think it's because I use a different kernel. Faux123.
Maybe this helps a bit
Sent from the gt9505 galaxy s4
Mr.AFK said:
Can I use this method initially?
So flash your recovery on stock rom, boot into it, "enable root procedure", boot up und go to play an install superuser app?
That's all?
Gesendet mit meinem S IV
Click to expand...
Click to collapse
You could simply flash a superuser CWM zip with any recovery and you`re rooted.
Sent from my Xperia Arc S using xda premium
I am downloading the whole ROM to check a bit more the stock boot.img
Also, I think it is better to move some exfat modules to the ramdisk to avoid mounting /system which always ends up in some issues
Also, need to look at some scripts that could be needed on start
When I am done, I will release another repack
Thabk you @Chenglu for the support, I appreciate it a lot
Note: this phone is a bit different from i9500, and since I do not own one to test, it could be we need some debugging until it is done
EDIT: Here's the recovery thread.
Original post:
So, let me preface this with the following statements:
I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices
So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-06 07:55 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6
I then used:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img
I then used the CWM Recovery Builder to build a basic recovery.
I took that image, pushed to /sdcard/rec.img and tried the following as root:
Code:
flash_image recovery /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
So I tried dd instead:
Code:
dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16
Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.
I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.
So if someone wouldn't mind pointing me in the right direction, that would be awesome.
Nobody?
METDeath said:
Nobody?
Click to expand...
Click to collapse
If you could upload the recovery.img, boot.img, as well as the output of "cat /proc/partitions", I'll have a custom recovery for you in as long as it takes for my computer to build it!
Also, if you could get me /proc/config.gz, that would be awesome.
cooldudezach said:
If you could upload the recovery.img, boot.img, as well as the output of "cat /proc/partitions", I'll have a custom recovery for you in as long as it takes for my computer to build it!
Also, if you could get me /proc/config.gz, that would be awesome.
Click to expand...
Click to collapse
Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.
It was literally two days outside of the return to store window too.
METDeath said:
Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.
It was literally two days outside of the return to store window too.
Click to expand...
Click to collapse
If you still have the phone, I can probably still save it. I've already saved 4 devices that are based on the same hardware this phone is (ZTE Awe, ZTE Sourcex2, ZTE Warp4g), and they were worse off
Especially if you can get into FTM mode, that means the boot.img is still functioning properly, just there is something causing the phone to loop. I'm assuming it loops while trying to get into recovery? Where did you get the factory.img?
---------- Post added at 11:53 AM ---------- Previous post was at 11:43 AM ----------
METDeath said:
So, let me preface this with the following statements:
I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices
So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-06 07:55 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6
I then used:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img
I then used the CWM Recovery Builder to build a basic recovery.
I took that image, pushed to /sdcard/rec.img and tried the following as root:
Code:
flash_image recovery /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
So I tried dd instead:
Code:
dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16
Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.
I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.
So if someone wouldn't mind pointing me in the right direction, that would be awesome.
Click to expand...
Click to collapse
I figured I'd go ahead and answer you problems/questions here.
First off, flash_image isn't going to work, stop using it. Second, fastboot flash doesn't work on this line of devices, again, stop using it.
When using dd, you should always zero out the partition first to make sure you aren't leaving behind anything from what was there before:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p16
The reason it's 'back' to 16MB, is because that is the size of the partition. It's just got a lot of 0's on the end. Everytime you pull it, it will always end up as a 16MB image. If you still have a copy of the stock recovery.img you pulled, I would appreciate a copy
cooldudezach said:
If you still have the phone, I can probably still save it. I've already saved 4 devices that are based on the same hardware this phone is (ZTE Awe, ZTE Sourcex2, ZTE Warp4g), and they were worse off
Especially if you can get into FTM mode, that means the boot.img is still functioning properly, just there is something causing the phone to loop. I'm assuming it loops while trying to get into recovery? Where did you get the factory.img?
---------- Post added at 11:53 AM ---------- Previous post was at 11:43 AM ----------
I figured I'd go ahead and answer you problems/questions here.
First off, flash_image isn't going to work, stop using it. Second, fastboot flash doesn't work on this line of devices, again, stop using it.
When using dd, you should always zero out the partition first to make sure you aren't leaving behind anything from what was there before:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p16
The reason it's 'back' to 16MB, is because that is the size of the partition. It's just got a lot of 0's on the end. Everytime you pull it, it will always end up as a 16MB image. If you still have a copy of the stock recovery.img you pulled, I would appreciate a copy
Click to expand...
Click to collapse
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
Thanks! So does your phone boot normally, or does it bootloop? I wasn't sure when you wrote that if you were just referring to the recovery boot or not. FTM is integrated with boot.img, which is why i am confused lol.
I'm just trying to figure out what's wrong exactly so I can get your phone up and running.
If you want to hop into irc chac #zte8930 on freenode, that's where I hang out, and where the devs for this group of phones also hangout.
For anyone looking in on this, the problem was fixed and there is now a PhilZ CWM for the phone.
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
is that can be use？i want to transplant a msm8960 device's rom so i need a custom recovery.
chongbos said:
is that can be use？i want to transplant a msm8960 device's rom so i need a custom recovery.
Click to expand...
Click to collapse
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
METDeath said:
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
Click to expand...
Click to collapse
so..can i flash this .img to my z995? is that offical or custom?
ATTACHED FILES
zte 995 stock recovery.zip - [Click for QR Code] (6.83 MB, 9 views)
thanks.sorry for my poor english!
---------- Post added at 10:13 AM ---------- Previous post was at 10:09 AM ----------
METDeath said:
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
Click to expand...
Click to collapse
oh,i have been focus on this forum for a long time,and now i have found it.thank u a lot.
---------- Post added at 10:24 AM ---------- Previous post was at 10:13 AM ----------
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
btw.
can u help me?
i have an old device GT-i9008L.it's a custom-made device from GT-i9003.
For now im willing to transplant a custom rom so im making a custom recovery before it.
but i cant let recovery mount SDcard...maybe i dont know how to editor it.
can u help me?only transplant i9003's custom recovery can take it easy.
thanks. sorry for my poor english!
chongbos said:
so..can i flash this .img to my z995? is that offical or custom?
ATTACHED FILES
zte 995 stock recovery.zip - [Click for QR Code] (6.83 MB, 9 views)
btw.
can u help me?
i have an old device GT-i9008L.it's a custom-made device from GT-i9003.
For now im willing to transplant a custom rom so im making a custom recovery before it.
but i cant let recovery mount SDcard...maybe i dont know how to editor it.
can u help me?only transplant i9003's custom recovery can take it easy.
thanks. sorry for my poor english!
Click to expand...
Click to collapse
The attached is the official recovery for the ZTE Z995 Overture (code name becky) that was sold in the US, so it's in English, it's also not a flashable zip as it's just the output of the dd command from the shell compressed into a zip file for smaller size.
I'm afraid I'm not able to help much with creating your own custom recovery as I'm not a developer. Perhaps you should create your own thread with more details on your phone.
Your English is actually better than some native English speakers, so keep up the practice and good work!
METDeath said:
The attached is the official recovery for the ZTE Z995 Overture (code name becky) that was sold in the US, so it's in English, it's also not a flashable zip as it's just the output of the dd command from the shell compressed into a zip file for smaller size.
I'm afraid I'm not able to help much with creating your own custom recovery as I'm not a developer. Perhaps you should create your own thread with more details on your phone.
Your English is actually better than some native English speakers, so keep up the practice and good work!
Click to expand...
Click to collapse
hah，it's really funny to met u.
i will back contact u~~~~
thanks.
Hmmmm METdeath, perhaps you could enlighten me (pm) the whereabouts of said recovery and other useful info.
If wanted a custom recovery and ROM on this phone since day 1 . I kinda gave up on any hope for it. Please any information to lead me in the correct direction would be greatly appreciated.
METDeath said:
For anyone looking in on this, the problem was fixed and there is now a PhilZ CWM for the phone.
Click to expand...
Click to collapse
Where is a link to this recovery?
Does anybody know where to get a firmware for new ZTE devices, like Z995, Z993, z740 etc?
Hello Help PLZ!!
Hello, I have a softed bricked zte overture z995. I saw in one of your replies you are familiar with reflashing this ROM. Is there any possible way that you can help guide me in fixing this problem? I'm not too familiar with all the concepts. I will be forever grateful!!! THanks!
~Caleb
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
Updated first post with the URL to the recovery.
Hi, anyone can help me to backup IMEI before flash ROM?
Please, I once made my IMEI lost after flash so i really glad to know how to backup IMEI first.
Thanks.
You can use TWRP-recovery to backup and restore your EFS partition (where the imei is stored) or use Samsung Tools (http://d-h.st/zGr)
can it also be done via ADB ??
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img
Code:
[email protected]:/dev/block/platform/dw_mmc.0/by-name # ll
ll
lrwxrwxrwx root root 2014-08-10 10:18 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-08-10 10:18 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-08-10 10:18 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-08-10 10:18 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-08-10 10:18 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-08-10 10:18 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-08-10 10:18 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-08-10 10:18 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-08-10 10:18 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-08-10 10:18 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-08-10 10:18 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-08-10 10:18 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-08-10 10:18 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-08-10 10:18 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-08-10 10:18 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-08-10 10:18 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-08-10 10:18 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-08-10 10:18 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-08-10 10:18 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-08-10 10:18 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-08-10 10:18 m9kefs3 -> /dev/block/mmcblk0p6
and if so how can it be restored ? (i am a Linux noob)
Hello.
So, as I described here, I success got root on this device. Now, I want a full backup in case things going bad. And obvious, a way to restore this backup.
I was searching for days for a ROM, but it simply don't exist (yet). This model have an identification (alps l1 mp6 v2 gxq6580 weg l p69) wich is used in some other devices (includings Samsung clones), so, I checked all the ROMs I found looking into /system partition on my device and comparing with /system image of the ROMs (I used SuperR's Kitchen), and none of them are equal, I mean, a lot of files (includind build.prop) are different, so there is a great chance to brick my phone if I use it.
Even if it is found, I can't restore with SP Flash Tools, because it don't work with this phone. I tried to readback, but it recognizes but never start. As the phone is a MT6580 based SoC, maybe is compatability issue also. MTK Droid Tools don't work also. It recognizes, but can't do anything (don't generate scatter, don't root, don't nothing), again maybe a compatibility also.
The stock recovery have no option to backup, and I'm afraid to flash a CWM or TWRP, because I don't know much about porting these things, and I don't have much information about partitions and these things yet. ADB while in recovery give me an unauthorized device, by the way.
The phone accept fastboot commands, but don't accept the 'fastboot boot image.img", to try a temporary recovery, it only accept the 'fastboot flash image.img'. As sayed on the thread above, the bootloader is now unlocked, by the way.
So... this the situation... Can't have backup for now. If it help you to help me, there is the result of ls -all /dev/block/platform/mtk-msdc.0/by-name/ command in adb shell:
Code:
1|[email protected]_weg_l:/ # ls -all /dev/block/platform/mtk-msdc.0/by-name/
lrwxrwxrwx root root 2017-03-30 00:16 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2017-03-30 00:16 cache -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2017-03-30 00:16 expdb -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2017-03-30 00:16 flashinfo -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2017-03-30 00:16 frp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2017-03-30 00:16 keystore -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2017-03-30 00:16 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2017-03-30 00:16 logo -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2017-03-30 00:16 metadata -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2017-03-30 00:16 nvdata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2017-03-30 00:16 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2017-03-30 00:16 oemkeystore -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2017-03-30 00:16 para -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2017-03-30 00:16 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2017-03-30 00:16 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2017-03-30 00:16 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2017-03-30 00:16 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2017-03-30 00:16 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2017-03-30 00:16 secro -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2017-03-30 00:16 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2017-03-30 00:16 userdata -> /dev/block/mmcblk0p20
[email protected]_weg_l:/ #
I sucessfully (I think) dump a boot image with dd command (dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img), but I'm not sure it is 100% perfect and if it can be safely used to restore (and how to restore... maybe 'fastboot flash'?). Maybe I can dump some other images, but I don't tried yet.
If you need any other information, I reply in almost same time.
Thanks in advice.
So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!
romulocarlos said:
So, I did a dd to dump boot and recovery, and open them sucessfuly on kitchen. Unfortunally, I can't do the same with system because adb only works with phone in normal mode.
Anyway to get the system for this phone? And, can I use these dumped files with 'fastboot flash' command?
Thanks!
Click to expand...
Click to collapse
Hello, i have recently posted a complete ROM on needrom. https://www.needrom.com/download/sony-xperia-c6-clone-mt6580/
i guess that is the one your are looking for. Good luck and sorry for my bad englich.
Help
Rom is corrupted, is not it? It's working? tell me how to download, I thank you